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

swarm-pr-review

Skill517 starsChanged 3 days agoMITView on GitHub

Thin adapter for the canonical swarm-pr-review skill. The authoritative workflow lives in .opencode and this file only preserves the mirror contract for Claude-side skill discovery.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    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/swarm-pr-review/SKILL.md as the canonical workflow.

    line 11
  2. Very specific:

    Keep the canonical workflow in .opencode.

    line 15
  3. Very specific:

    Only if this session actually exposes the swarm controller tools, use dispatch_lanes_async, collect_lane_results, and retrieve_lane_output.

    line 16
  4. Very specific:

    If the controller is absent, treat that as Profile B, not an error: use the native Agent/Task subagent tool flow, keep the PR publication …

    line 17

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

Swarm PR Review

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

Claude Code Execution Notes

  • This adapter is a thin shim only.
  • Keep the canonical workflow in .opencode; do not duplicate protocol text here.
  • Only if this session actually exposes the swarm controller tools, use dispatch_lanes_async, collect_lane_results, and retrieve_lane_output; direct-Task dispatch are not equivalent to that controller path.
  • If the controller is absent, treat that as Profile B, not an error: use the native Agent/Task subagent tool flow, keep the PR publication contract intact, and never report BLOCKED merely because the controller is unavailable.
  • For exact-head provenance, verify the commit with git rev-parse --verify <full_pr_head_sha>^0 and git cat-file -t <full_pr_head_sha>.
  • Preserve the canonical workflow reference above so drift checks can verify delegation.

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