Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Detects optimal commit type from git changes. Use when analyzing commits, determining commit type, or before committing.
Complete development branches with structured options for merge, PR, keep, or discard. WHEN: MUST use when implementation complete and tests pass. Invoke with "/finishing-a-development-branch" or "finish this branch", "ready to merge", "what to do with this branch". WHEN NOT: Tests still failing, implementation incomplete, still debugging.
Initialize a new BDD-based CLI project using cookiecutter templates from Git repositories. This skill intelligently selects and fetches the appropriate template based on user requirements, supporting templates distributed across multiple Git projects.
Creates a pull request from the current branch to the main branch.
Generate a commit message for changes already in the Git staging area, and await approval from the user. Use when the agent needs to generate a commit message for staged changes. Only generates the commit message, but does not perform the commit.
Manage git worktrees for isolated development. Use when creating isolated workspaces, managing parallel development, handling worktree lifecycle, or merging completed work.
Process all PR feedback in one pass. Fetches review comments and CI failures together, creates a unified action plan, applies fixes, replies to reviewers, resolves threads, and posts a summary. Use when asked to address PR feedback, fix review comments, handle CI failures, or process PR reviews. Works on the current branch's open PR.
Rules for file organization, naming conventions, and environment variables.
Create and manage Git worktrees to parallelize agent tasks safely. Use when you need multiple concurrent checkouts (sub-agents, parallel edits, or isolated experiments) and want deterministic setup/cleanup with manifests and logs.
Set up a GitHub issue for development with branch, worktree, and planning doc. Use when user says "start issue", "work on issue
Guidance for initializing new projects. Use framework/package manager commands instead of manual scaffolding.
Check PR review comments and feedback from CodeRabbit and human reviewers. Use when user asks about reviews, unresolved comments, CodeRabbit feedback, Claude review, or PR status.
Self-review patterns and checklists. Use before creating PRs or when reviewing your own changes.
Enforces commit guardrails ensuring traceability and security.
Commit/change description convention (KCC) with Subsystem + Type + Ticket formatting, lint rules, and VCS-agnostic guidance.
Use when investigating merge conflicts, reducing communication overhead, detecting modules with high coordination complexity, or identifying files edited by many contributors and cross-team - reveals coordination bottlenecks and team communication issues
Process ephemeral session notes and extract valuable knowledge into permanent documentation
Create professional git commits following conventional commit format with proper staging and verification
