PR Toolkit
An orchestrator skill that routes pull request review tasks to the appropriate specialized sub-skill.
When to Use
Use this skill when:
- •Reviewing a pull request for overall quality
- •Preparing code for merge
- •Running a comprehensive pre-merge checklist
- •Unsure which specific review tool to use
Available Sub-Skills
| Sub-Skill | Purpose | When to Use |
|---|---|---|
| code-reviewer | Guideline compliance and bug detection | After writing code, before committing |
| code-simplifier | Clarity and maintainability refinement | After completing a coding task |
| comment-analyzer | Documentation accuracy verification | After adding/modifying comments or docs |
| pr-test-analyzer | Test coverage gap analysis | After creating or updating a PR |
| silent-failure-hunter | Error handling and silent failure audit | When code has try/catch, fallbacks, or error handling |
| type-design-analyzer | Type invariant and encapsulation quality | When introducing or modifying types |
Recommended Workflow
For a thorough PR review, run the sub-skills in this order:
- •code-reviewer - Catch guideline violations and bugs first
- •silent-failure-hunter - Ensure error handling is robust
- •type-design-analyzer - Verify type design quality
- •pr-test-analyzer - Identify test coverage gaps
- •comment-analyzer - Verify documentation accuracy
- •code-simplifier - Final clarity pass
Project Context
This project uses:
- •Angular 21 with standalone components and signals
- •TypeScript ~5.9 with strict mode
- •Vest.js for validation
- •Vitest for unit testing
- •Playwright for E2E testing
- •Tailwind CSS v4 for styling
Review against the project's guidelines in .github/instructions/ and .github/copilot-instructions.md.