agentleFS
kostiantyn-matseborakostiantyn-matsebora/canopy-examples/.agents/skills/parallel-review/SKILL.md

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

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
  1. Distinctive:

    Only report what is observable in the provided files — do not speculate

    line 54

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Runtime required. This skill uses Canopy tree notation; canopy-runtime must be active.

Detect canopy-runtime — present if either:

  • canopy-runtime/SKILL.md exists under .claude/skills/, .github/skills/, or .agents/skills/, OR
  • a canopy-runtime marker block exists in CLAUDE.md or .github/copilot-instructions.md.

If neither is present — install canopy-runtime first (see the compatibility field for the source and install options), then re-invoke this skill.

Do not interpret the ## Tree without 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.md

Rules

  • 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_FINDINGS relies on stable names, not arrival timing
  • A single subagent failure does not abort siblings (Promise.allSettled) — MERGE_ASPECT_FINDINGS handles 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.