agentleFS
Sign inStart free
ZaxbyHubZaxbyHub/opencode-swarm/.claude/skills/codebase-review-swarm/SKILL.md

codebase-review-swarm

Skill517 starsChanged 3 days agoMITView on GitHub

Claude Code adapter for running a rigorous, quote-grounded codebase review or security/QA/accessibility/performance/AI-slop/enhancement audit. Use for full-repo or large-subsystem review reports; not for normal implementation.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read and follow ../../../.opencode/skills/codebase-review-swarm/SKILL.md as the canonical workflow.

    line 13
  2. Distinctive:

    Treat this as a read-only review workflow.

    line 18
  3. Very specific:

    Write review artifacts only under .swarm/review-v8/runs/<run_id>/.

    line 19
  4. Distinctive:

    Run Phase 0 inventory first and stop for review-mode selection unless the user already selected tracks and explicitly authorized continuing.

    line 20
  5. Distinctive:

    Use independent reviewer and critic passes before finalizing report findings.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.

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

Codebase Review Swarm

Read and follow ../../../.opencode/skills/codebase-review-swarm/SKILL.md as the canonical workflow.

Claude Code Execution Notes

  • Treat this as a read-only review workflow. Do not modify source files.
  • Write review artifacts only under .swarm/review-v8/runs/<run_id>/.
  • Run Phase 0 inventory first and stop for review-mode selection unless the user already selected tracks and explicitly authorized continuing.
  • Preserve the skill's evidence rule: no quote, no claim.
  • For dispatch lanes, only if the session actually exposes the controller's lane tools, treat output as a preview and call retrieve_lane_output for full output_ref artifacts before consuming ledgers, counting candidates, routing validation, or declaring coverage clean; when those tools are absent, treat inline output as the full artifact and disclose any truncation as an explicit coverage limitation.
  • Use independent reviewer and critic passes before finalizing report findings.

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.

Check your setup, free