You can turn any GitHub issue into a clear technical plan. This skill fetches the issue details, looks at your code, and writes a full specification. It helps developers and teams understand what needs to be built.
The specification includes the problem, technical approach, and step by step implementation. It also lists tests, files to change, and success criteria. Everything is saved in a specs folder for your team to review.
Use this tool to save time and avoid misunderstandings. It follows best practices like test driven development and keeps files under 300 lines. This makes your project easier to manage.
Global
mkdir -p ~/.claude/skills/analyze-issueProject
mkdir -p .claude/skills/analyze-issueSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective