review-file
Skill0 starsChanged 6 months agoMITView on GitHub
Perform a structured code review of a file or directory. Reports issues grouped by severity (critical / warning / info) with concrete suggested fixes. Use before opening a pull request or after significant changes.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- add-changelog-entrySkill
- bump-versionSkill
- canopy-debugSkill
- canopy-runtimeSkill
- canopySkill
- generate-readmeSkill
- parallel-reviewSkill
- scaffold-skillSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 45
Only report what is observable in the provided files — do not speculate
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Runtime required. This skill uses Canopy tree notation; canopy-runtime must be active.
Detect canopy-runtime — present if either:
canopy-runtime/SKILL.mdexists under.claude/skills/,.github/skills/, or.agents/skills/, OR- a canopy-runtime marker block exists in
CLAUDE.mdor.github/copilot-instructions.md.If neither is present — install canopy-runtime first (see the
compatibilityfield for the source and install options), then re-invoke this skill.Do not interpret the
## Treewithout canopy-runtime active.
Review: $ARGUMENTS
Tree
review-file
├── **EXPLORE** >> context
├── SHOW_PLAN >> target | file_count | critical_count | warning_count | info_count
├── Read `assets/policies/review-rules.md` for severity classification rules
├── IF << critical findings present
│ └── REPORT_FINDINGS << critical
├── IF << warning findings present
│ └── REPORT_FINDINGS << warning
├── IF << info findings present
│ └── REPORT_FINDINGS << info
└── IF << no findings at any severity
└── report from `assets/constants/no-findings-message.md`Rules
- Only report what is observable in the provided files — do not speculate
- Suggested fixes must be concrete: show the corrected code snippet, not just a description
Response: target | critical | warnings | info | overall_verdict
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.

