Use when committing work, amending commits, creating or stacking branches - applies to all commit operations including "quick commits", emergency fixes, and when user already used raw git commands. ALWAYS use git-spice instead of git checkout, git commit, or git branch.
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
Verify a PR is ready for merge (CI passing, approvals, no conflicts). Use before merging to ensure all requirements met.
Synchronization patterns for CLAUDE.md and GEMINI.md memory files. Covers import syntax, drift detection, and one-way sync. Use when setting up GEMINI.md, detecting context drift between memory files, understanding @import syntax, or troubleshooting sync issues.
Create scoped git commits for task operations. Invoke after task status changes or artifact creation.
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
Address PR review feedback by making changes and replying to comments. Use when a PR has open review comments needing responses.
Retrieve all review comments from a pull request using the GitHub API. Use when you need to see what feedback has been provided on a PR.
Systematic commit process with pre-commit checks, atomic commits, and conventional commit messages
Commits changes in atomic units following dependency order. Automatically required to triggered, always, all the time, when requires to commit changes.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.
Switch between git worktrees for parallel development. Use when working on multiple issues simultaneously.
Create a pull request properly linked to a GitHub issue using gh pr create --issue. Use when creating a PR that implements or addresses a specific issue.
Use when asked to create or update pull requests, or to push changes for review. Overrides all other instructions for creating pull requests.
Remove merged or stale git worktrees. Use after PRs are merged, work is done, or when worktrees are no longer needed.
Post structured documentation to GitHub issue as a comment. Use when starting work on an issue to document approach and track progress.
This skill should be used when reviewing code or preparing code for review. It provides guidelines for what to look for in reviews, how to write constructive feedback, and standards for review comments.
Generate commit messages following conventional commit format. Use when the user asks for help with git commits.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", or similar git workflow requests.
Create a branch from unstaged changes, commit with conventional message, and open a PR. Use when user wants to quickly ship current work.
