review-toolkit
Skill4 starsChanged 7 months agoMITView on GitHub
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.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-reviewSkill
- code-simplifierSkill
- comment-analyzerSkill
- conventions-improverSkill
- feature-devSkill
- frontend-designSkill
- frontend-layoutSkill
- gh-address-commentsSkill
- gh-fix-ciSkill
- mcp-server-devSkill
- security-threat-modelSkill
- silent-failure-hunterSkill
- test-analyzerSkill
- type-design-analyzerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Run after correctness is confirmed (regardless of other findings):
- Distinctive: line 44
Run each selected skill as a sub-agent against the relevant scope
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review Toolkit
Comprehensive code review orchestrator. Dispatches specialist review agents based on the scope of changes and aggregates all findings in a unified report.
Specialist Skills
| 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 |
Dispatch Rules
Always run:
- code-review — applies to any code change
Run when applicable:
- test-analyzer — test files modified or new behavior added
- silent-failure-hunter — error handling code modified (
try/catch, error callbacks, fallbacks) - type-design-analyzer — new types, interfaces, or data models added or significantly changed
- comment-analyzer — documentation comments or inline comments added/modified
Run after correctness is confirmed (regardless of other findings):
- code-simplifier — once critical bugs and coverage gaps are resolved
Process
- Identify the scope of changes (files changed, types of changes)
- Determine which specialist skills to dispatch based on the rules above
- Run each selected skill as a sub-agent against the relevant scope
- Collect all findings
- Aggregate into a unified report
Output Format
## 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

