merge-conflict-resolution
Use when git merge or rebase fails with conflicts, you see 'unmerged paths' or conflict markers (<<<<<<< =======), or need help resolving conflicted files
nim-pr-guide
>
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
subagent-prompting
>
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans
using-lsp-tools
Use when mcp-language-server tools are available and you need semantic code intelligence for navigation, refactoring, or type analysis
using-skills
Use when starting any conversation to establish skill discovery patterns
worktree-merge
Use when merging parallel worktrees back together after parallel implementation with interface contracts
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Page 2 of 2 · 31 results