Loading...
Loading...
Found 3,276 Skills
Analyse code changes since the last docs update and refresh the project's documentation files. Use when code has changed and documentation needs to be updated, after implementing new features, or before a milestone commit.
Explains the intent behind source code by finding original session transcripts. Use explain with a function, file, or line of code to understand why it exists.
Publish a generated CLI to the printing-press-library repo
CI/CD Pipeline Builder
Detects hardcoded secrets, API keys, passwords, and credentials in source code. Use when checking for leaked secrets, credential exposure, or before committing code.
Intelligently analyze code changes and split them into multiple logical commits based on functionality and change types. This skill should be used when users want to commit code changes, especially when there are multiple unrelated changes in the working directory.
Author's cleanup checklist before committing or submitting a PR. Use before any commit or PR to ensure code is clean, focused, and ready for review. Checks for debug code, secrets, redundant changes, and scope creep.
[Review & Quality] ⚡⚡⚡ Two-pass code review for task completion
Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers, monitors progress, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.
GainForest beads (`bd`) planning workflow. Activates on ALL user work requests — task planning, epic management, claiming work, closing tasks with commit links, handling blockers. Use before writing any code.
Verify all implementation is done, then deliver the plan. Part of the Plot workflow. Use on /plot-deliver.
Verify release readiness and guide the release process. Part of the Plot workflow. Use on /plot-release.