Find the right skill and sequence for your current development task, from shaping an idea to implementation, debugging, and review. The guide also explains when to prototype, prepare specifications, or move work into a fresh session.
- Choose a workflow for turning an idea into working software
- Find the starting point for a difficult bug investigation
- Plan specifications and tickets for work across multiple sessions
vinvcn/mattpocock-skills-zh-CN☆ 5.2KUpdated Oct 20, 2026
Review changes from a chosen Git reference against both project coding standards and issue or specification requirements. Separate parallel reviews report rule violations, possible design problems, missing requirements, and changes beyond the intended scope.
- Review a branch or pull request
- Check changes since a specific commit
- Find missing requirements or unintended scope
vinvcn/mattpocock-skills-zh-CN☆ 5.2KUpdated Oct 20, 2026
Design modules that expose simple interfaces while hiding substantial behavior. Use shared terms and principles to assess interface complexity, decide where behavior can be swapped, and organize code so callers and tests use the same interface.
- Simplify a module interface
- Review module structure during refactoring
- Decide where behavior should be swappable
vinvcn/mattpocock-skills-zh-CN☆ 5.2KUpdated Oct 20, 2026
Diagnose difficult bugs and performance regressions by first building a repeatable check for the exact symptom. Minimize the reproduction, test ranked hypotheses, apply a fix, and verify the original scenario with regression tests where suitable.
- Investigating persistent errors or incorrect output
- Increasing reproduction rates for intermittent bugs
- Measuring and diagnosing performance regressions
vinvcn/mattpocock-skills-zh-CN☆ 5.2KUpdated Oct 20, 2026
Clarify project terminology and the relationships between business concepts. Check definitions against concrete scenarios and code, update GLOSSARY.md as terms are agreed, and record significant design decisions with their trade-offs when the stated criteria are met.
- Clarifying ambiguous project terminology
- Creating or updating GLOSSARY.md
- Checking concept boundaries against code and edge cases
vinvcn/mattpocock-skills-zh-CN☆ 5.2KUpdated Oct 20, 2026
Set up Claude Code hooks that block specified Git commands before they run, including push and destructive cleanup operations. Choose project or global installation, adjust the blocked commands, and test that the hook rejects a sample command.
- Blocking git push from Claude Code
- Preventing commands that discard local changes
- Installing Git guardrails across projects
vinvcn/mattpocock-skills-zh-CN☆ 5.2KUpdated Oct 20, 2026