Loading...
Loading...
Found 3,092 Skills
Create or update a pull request for the current branch with a summary of all changes.
This skill should be used when a developer wants to autonomously execute all tasks under a fully-specified Epic or Feature — for example "go", "start building", "implement everything", "run the loop", "execute the feature", "build it all", "kick it off". Requires that the Epic/Feature/Task tree is fully written before starting. Chains implement → verify → PR for every task in dependency order, with targeted human-in-the-loop gates for contradictions and ambiguities.
Remove AI-generated code slop from a branch. Use when cleaning up AI-generated code, removing unnecessary comments, defensive checks, or type casts. Checks diff against main and fixes style inconsistencies.
Track tasks and issues using the bd CLI. Use for task management, sprint planning, dependency tracking, and project organization. Replaces TodoWrite.
Query DeepWiki for repository documentation and structure. Use to understand open source projects, find API docs, and explore codebases.
Translate new entries in XLF files. Finds state="new" in changed messages.{LANG}.xlf files, shows context, proposes translations for review.
This skill should be used when the user asks to "start a feature", "create feature branch", "begin new feature", "git flow feature start", or wants to start working on a new feature branch.
Task Planning Specification, applicable to complex tasks (≥3 steps), including requirement decision-making and project plan creation. It covers planning specifications, requirement decision-making processes, and project plan generation tools.
Game development tools, asset pipelines, version control, build systems, and team development workflows for efficient production.
Fix bug command
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or runs /commit-staged or /commit-creator commands.
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point