docker-local-troubleshoot
Diagnose and fix docker-local issues - container failures, connectivity problems, port conflicts, and configuration errors
Diagnose and fix docker-local issues - container failures, connectivity problems, port conflicts, and configuration errors
create git worktree with new branch. use when working on features in parallel, isolating experimental work, or avoiding stash/switch overhead. creates sibling directory.
Perform a shallow clone of a Git repository to a temporary location.
Read context from GitHub issue including body and comments. Use before starting implementation work or when prior context is needed.
Create isolated git worktrees for parallel development. Use when working on multiple issues simultaneously.
Create changelog from git commits. Use when preparing release notes.
Use when writing or improving messages for Git commits, or when asked to generate a commit message or pull request description.
Sync git worktrees with remote and main branch changes. Use to keep long-running feature branches up-to-date.
reimplement current branch with clean, narrative-quality git commit history. use when commit history is messy, after exploratory work, or before PR review. creates new branch with logical, atomic commits.
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.