parallel-review
Skill0 starsChanged 6 months agoMITView on GitHub
Multi-aspect code review using PARALLEL fan-out — runs four independent review subagents concurrently (security / performance / style / correctness), each in its own context window, then merges findings into a unified severity-grouped report. Demonstrates the subagent dispatch model (per-op markers + bold call-sites) introduced in canopy v0.20.0.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- danieleteti/delphimvcframeworktheir own version, first seen Nov 2, 2026
- stoa-platform/stoatheir own version, first seen Nov 1, 2026
- akshaypimprikar/pragmatheir own version, first seen Sep 29, 2026
- bhagyamudgal/skillstheir own version, first seen Sep 9, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- danieleteti/delphimvcframework★ 1.4ksame name
- stoa-platform/stoa★ 9same name
- akshaypimprikar/pragma★ 4same name
- bhagyamudgal/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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
- review-fileSkill
- scaffold-skillSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
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 54
Only report what is observable in the provided files — do not speculate
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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.
Parallel-review target: $ARGUMENTS
Tree
parallel-review
├── **EXPLORE_TARGET** << $ARGUMENTS >> context
├── SHOW_PLAN >> target | file_count | aspects
├── ASK << Proceed with parallel review? | Yes | No
├── IF << user chose No
│ └── END Cancelled.
├── Read `assets/constants/review-aspects.md` for per-aspect criteria
├── PARALLEL
│ ├── **REVIEW_ASPECT** << "security" | context.files >> security_findings
│ ├── **REVIEW_ASPECT** << "performance" | context.files >> perf_findings
│ ├── **REVIEW_ASPECT** << "style" | context.files >> style_findings
│ └── **REVIEW_ASPECT** << "correctness" | context.files >> correctness_findings
├── MERGE_ASPECT_FINDINGS << security_findings | perf_findings | style_findings | correctness_findings >> all_findings
├── REPORT_BY_SEVERITY << all_findings
└── VERIFY_EXPECTED << assets/verify/verify-expected.mdRules
- Each bold-marked op call (
**EXPLORE_TARGET**,**REVIEW_ASPECT**) dispatches as a subagent — its own context window, no access to parent state outside its<<inputs - PARALLEL children that are bold-marked op calls fan out as parallel subagents in a single agent turn
- Bindings (
>>) in PARALLEL children are merged in declaration order regardless of completion order —MERGE_ASPECT_FINDINGSrelies on stable names, not arrival timing - A single subagent failure does not abort siblings (
Promise.allSettled) —MERGE_ASPECT_FINDINGShandles missing/empty aspects gracefully - Suggested fixes must be concrete: show the corrected code snippet, not just a description
- Only report what is observable in the provided files — do not speculate
Response: target | aspects_reviewed | 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.

