A curated collection of Claude Code skills and prompt templates designed to streamline software engineering workflows. These skills leverage Claude's advanced capabilities to provide automated code analysis, design reviews, security scanning, and comprehensive documentation generation.
-
Clone or download this repository:
git clone https://github.com/yourusername/claude-tools.git
-
Copy skills to your Claude Code settings (Option A - Per Project):
# Copy the skills directory to your project cp -r claude-tools/skills /path/to/your/project/.claude/ -
Or use as a global skills library (Option B):
# Copy to your global Claude Code directory cp -r claude-tools/skills ~/.claude/
-
Verify installation:
- Open your project in Claude Code
- The skills should be available based on context triggers or explicit invocation
Directory: skills/code-review/
Performs senior-engineer-grade PR code reviews covering correctness, security, performance, testing, design, and observability.
Triggers: Review a pull request, PR, merge request, diff, branch, or code changes
Key Features:
- Multi-dimensional analysis (correctness, security, performance, design)
- File prioritization by risk (P0-P4)
- Severity classification (CRITICAL/HIGH/MEDIUM/LOW/PRAISE)
- Actionable recommendations with code suggestions
Directory: skills/codebase-review/
Performs a thorough codebase review and produces a prioritized to_do.md listing all bug fixes, improvements, and action items.
Triggers: Review, audit, or analyze a codebase for bugs, code quality issues, missing tests, TODOs, technical debt
Key Features:
- Systematic file-by-file review
- Bug detection (logical, security, performance)
- Test coverage gap identification
- .NET/C#-specific checks included
- Prioritized action item list
Directory: skills/dotnet-refactor/
Principal-level C#/.NET codebase refactoring with phased plans and regression safety.
Triggers: Refactor, restructure, clean up, or improve C#/.NET code quality
Key Features:
- Discovery of code smells and coupling hotspots
- Baseline unit test safety net
- Phased refactoring plan generation
- SOLID principles and design pattern guidance
- Logging and cross-cutting concern improvements
Directory: skills/security-scan/
Comprehensive security vulnerability assessment aligned with OWASP, CWE, and CVSS standards.
Triggers: Scan code for security issues, perform security review/audit, find vulnerabilities, check for OWASP Top 10 issues
Key Features:
- OWASP Top 10 vulnerability detection
- Multi-language support (JS/TS, Python, Java, Go, C/C++, Ruby, PHP, C#, Rust, Swift, Kotlin)
- Automated pattern scanning with manual deep-dive
- Dependency audit for known CVEs
- CVSS-aligned severity classification
Directory: skills/performance-analysis/
Analyzes application performance bottlenecks with focus on .NET diagnostics.
Triggers: Performance analysis, profiling, optimization recommendations
Key Features:
- Anti-pattern detection
- .NET-specific diagnostics
- Structured output template
- Actionable optimization recommendations
Directory: skills/architecture-review/
Generates industry-standard architecture design documents by analyzing codebases across structure, patterns, principles, and quality attributes.
Triggers: Review or analyze code architecture, create architecture overview, assess code quality, identify architectural strengths/weaknesses
Key Features:
- Systematic codebase exploration
- Design pattern identification (creational, structural, behavioral, architectural)
- Clean code principles assessment (SOLID, DRY, KISS, YAGNI)
- Quality attribute ratings (1-5 scale)
- Mermaid diagram generation
Directory: skills/design-doc-review/
Principal-engineer-level design document review against PRD requirements.
Triggers: Review, critique, or evaluate a design document, technical design, architecture proposal
Key Features:
- PRD alignment verification
- 11 review dimensions (architecture, security, scalability, availability, etc.)
- Severity-based issue classification (P0-P3)
- Actionable recommendations
Directory: skills/prd-to-design-doc/
Transforms Product Requirements Documents into Developer Design Documents following RFC conventions used by Google, Uber, Airbnb, Stripe, and others.
Triggers: Create a design document from a PRD, generate an RFC, create technical design doc
Key Features:
- Trade-off focused analysis
- Alternatives considered with comparison
- Cross-cutting concerns (security, privacy, observability)
- Phased rollout planning
- Mermaid architecture diagrams
Directory: skills/prd-generator/ | skills/code-to-prd-doc/
Reverse-engineers a codebase into a formal Product Requirements Document structured for Jira work item creation.
Triggers: Generate PRD, analyze codebase, document requirements, reverse-engineer features, prepare Jira epics from code
Key Features:
- Feature extraction by category
- Gap and technical debt identification
- Jira-ready epic/story/task breakdown
- .NET/C# specific analysis patterns
- Fibonacci story point estimation
Directory: skills/tdd-bugfix/
Fixes bugs using test-driven development methodology with strict adherence to project conventions.
Triggers: Fix a bug using TDD, safe bug fix with tests
Key Features:
- Project convention discovery
- Failing test creation before fix
- Project test framework/style matching
- Full regression test verification
Directory: skills/qa-test-plan-review/
Railway QA Lead Engineer skill for reviewing test plans against CENELEC EN 50716/EN 50128, EN 50126, and EN 50129 standards.
Triggers: Railway test plan review, CENELEC compliance testing, signaling test coverage, safety-critical test case generation
Key Features:
- SIL-graded requirement analysis
- Gap analysis against railway standards
- CSV test case generation matching input format
- Safety/fail-safe scenario coverage
Directory: skills/git-rebase-main/
Fetches and rebases current branch onto main/master with automatic stash handling.
Triggers: Update branch with main, sync with default branch, pull and rebase
Key Features:
- Auto-detects main vs master
- Automatic stash/unstash via
--autostash - Conflict resolution guidance
Directory: skills/keybindings-help/
Helps customize Claude Code keyboard shortcuts by editing ~/.claude/keybindings.json.
Triggers: Rebind keys, add chord bindings, customize keybindings, change submit key
Key Features:
- Complete keybindings.json reference
- All contexts and actions documented
- Chord binding support
- Common customization examples
Reusable prompt templates in the prompts/ directory:
| File | Purpose |
|---|---|
analyze_paper.md |
Academic paper analysis template |
architecture_analysis.md |
Comprehensive codebase architecture review |
design_document.md |
Design document generation template |
engineering_brief.md |
Daily engineering brief from Jira data |
claude-tools/
├── skills/ # Claude Code skills
│ ├── architecture-review/
│ │ ├── SKILL.md
│ │ └── references/
│ ├── code-review/
│ │ ├── SKILL.md
│ │ └── references/
│ ├── code-to-prd-doc/
│ │ ├── SKILL.md
│ │ ├── assets/
│ │ └── references/
│ ├── codebase-review/
│ │ └── SKILL.md
│ ├── design-doc-review/
│ │ ├── SKILL.md
│ │ └── references/
│ ├── dotnet-refactor/
│ │ ├── SKILL.md
│ │ └── references/
│ ├── git-rebase-main/
│ │ ├── SKILL.md
│ │ └── scripts/
│ ├── keybindings-help/
│ │ └── SKILL.md
│ ├── performance-analysis/
│ │ ├── SKILL.md
│ │ ├── references/
│ │ └── scripts/
│ ├── prd-generator/
│ │ ├── SKILL.md
│ │ ├── assets/
│ │ └── references/
│ ├── prd-to-design-doc/
│ │ └── SKILL.md
│ ├── qa-test-plan-review/
│ │ ├── SKILL.md
│ │ └── references/
│ ├── security-scan/
│ │ ├── SKILL.md
│ │ ├── references/
│ │ └── scripts/
│ └── tdd-bugfix/
│ └── SKILL.md
├── prompts/ # Reusable prompt templates
│ ├── analyze_paper.md
│ ├── architecture_analysis.md
│ ├── design_document.md
│ └── engineering_brief.md
├── workflow/ # Workflow documentation & assets
├── LICENSE
└── README.md
Each skill follows a consistent structure:
skill-name/
├── SKILL.md # Main skill definition with frontmatter and workflow
├── references/ # Supporting documentation and checklists
├── assets/ # Templates and output formats
└── scripts/ # Automation scripts (if applicable)
The SKILL.md file contains:
- Frontmatter: Name, description, and trigger conditions
- Workflow: Step-by-step execution process
- References: Links to supporting materials
- Productivity: Automate time-consuming analysis and documentation tasks
- Consistency: Standardized analysis approaches across all scenarios
- Thoroughness: Comprehensive coverage of quality, security, and performance dimensions
- Actionability: Prioritized recommendations with specific code examples
- Collaboration: Structured outputs perfect for team reviews and discussions
- Best Practices: Incorporates industry standards (OWASP, SOLID, CENELEC, etc.)
- Context Triggers: Skills activate automatically based on your request context
- Reference Files: Skills use supporting references for comprehensive analysis
- Customization: Edit SKILL.md files to adapt to your team's specific needs
- Iteration: Skills are designed for iterative refinement based on initial output
- Headless/CI Automation: Run the full agentic workflow non-interactively.
# Run the full workflow non-interactively
claude -p "
Implement rate limiting middleware on the ASP.NET Core API using
System.Threading.RateLimiting. Apply a fixed-window policy of
100 requests per minute per client IP on all /api/* endpoints.
Follow this workflow:
1. Use software-architect agent to produce implementation plan.
2. Use principal-engineer agent to review plan and implement with tests.
3. Use code-reviewer agent to review and fix all issues. If BLOCKED,
use principal-engineer to rework, then re-run code-reviewer.
4. Use test-runner agent to run all four test tiers.
5. If any tier fails, use principal-engineer to fix, then code-reviewer
to verify, then test-runner to re-test. Repeat until green.
Print WORKFLOW_SUCCESS if everything passes, WORKFLOW_FAILED otherwise.
" --allowedTools "Read,Write,Edit,Bash,Grep,Glob,MultiEdit" --output-format json
I need to add rate limiting middleware to the ASP.NET Core API using the built-in System.Threading.RateLimiting. Apply a fixed-window policy of 100 requests per minute per client IP on all /api/* endpoints. Please follow this workflow:
-
Use the software-architect agent to analyze the codebase and produce a detailed implementation plan with unit test strategy.
-
Use the principal-engineer agent to review and refine the plan, then implement the code changes with unit tests. Unit tests must pass.
-
Use the code-reviewer agent to review the implementation and fix any issues directly. Build and unit tests must pass after fixes. If the verdict is BLOCKED, use the principal-engineer agent to rework the implementation, then re-run the code-reviewer agent.
-
Use the test-runner agent to run all four test tiers (unit, functional, integration, pact).
-
If any tests fail due to the change, use the principal-engineer agent to fix them, then the code-reviewer agent to verify the fixes, then re-run the test-runner agent. Repeat until all tiers pass.
-
Summarize the final result.
-
Use principal-engineer agent to review plan and implement with tests.
-
Use code-reviewer agent to review and fix all issues. If BLOCKED, use principal-engineer to rework, then re-run code-reviewer.
-
Use test-runner agent to run all four test tiers.
-
If any tier fails, use principal-engineer to fix, then code-reviewer to verify, then test-runner to re-test. Repeat until green. Print WORKFLOW_SUCCESS if everything passes, WORKFLOW_FAILED otherwise.
We welcome contributions! When adding new skills:
- Follow the structure: Use the established SKILL.md format with frontmatter
- Be comprehensive: Include detailed workflow steps and references
- Provide clear triggers: Document what user requests activate the skill
- Include references: Add supporting documentation in a
references/subdirectory - Test thoroughly: Validate skills with real-world scenarios
- Update README: Add documentation for new skills to this file
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.
- Issues: Report bugs or request features via GitHub Issues
- Documentation: See Claude Code documentation for platform details
- Community: Share your custom skills and improvements!
Made for the engineering community