skills/review-toolkit/SKILL.md
Orchestrates a comprehensive code review using up to 6 specialist skills. Dispatches code-review, code-simplifier, comment-analyzer, silent-failure-hunter, type-design-analyzer, and test-analyzer based on the scope of changes. Use for thorough end-to-end review of code changes.
npx skillsauth add euxx/claude-skills-for-copilot review-toolkitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive code review orchestrator. Dispatches specialist review agents based on the scope of changes and aggregates all findings in a unified report.
| Skill | Purpose | | ------------------------- | --------------------------------------------------------------- | | code-review | Bugs, security issues, correctness, conventions-file violations | | code-simplifier | Unnecessary complexity, duplication, readability | | comment-analyzer | Comment accuracy, comment rot, misleading documentation | | silent-failure-hunter | Silent errors, inadequate user feedback, catch block quality | | type-design-analyzer | Type encapsulation, invariant expression and enforcement | | test-analyzer | Behavioral coverage gaps, test quality, anti-pattern detection |
Always run:
Run when applicable:
try/catch, error callbacks, fallbacks)Run after correctness is confirmed (regardless of other findings):
## Toolkit Summary
Specialists dispatched: [list]
Overall assessment: [PASS / NEEDS WORK / CRITICAL ISSUES]
## Critical Issues
[Aggregated CRITICAL findings from all specialists, with source skill noted]
## Important Issues
[Aggregated HIGH/IMPORTANT findings]
## Suggestions
[Aggregated MEDIUM/lower priority findings]
## Positive Observations
[Notable good practices found across all reviews]
Severity order: Critical → Important → Suggestions → Positive Observations.
testing
Analyzes type design quality by rating encapsulation, invariant expression, usefulness, and enforcement. Helps design types that make invalid states unrepresentable. Use when reviewing new types or data models.
testing
Reviews test coverage quality from a behavioral perspective, identifying critical gaps and test quality issues. Does not check line coverage — checks meaningful scenario coverage. Use after adding or modifying tests.
development
Audits error handling for silent failures, inadequate user feedback, and unjustified fallback behavior. Finds issues in catch blocks, fallbacks, and error paths. Use after modifying error handling code.
development
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.