agentleFS
syamanersyamaner/roastpilot-agent/.claude/skills/triage-pr/SKILL.md

triage-pr

Skill2 starsChanged 22 days agoMITView on GitHub

Independently triage the current PR's review feedback via the pr-triage subagent — which comments to address, defer, or reject, and whether it's mergeable. Use before merging an agent-team PR so the author never triages its own review (D23).

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. PinW/whisper-key-local★ 203same name
    2. block/proto-fleet★ 57same 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 repository9 other files it gives its agents.

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

    Read-only test execution and the incidental caches or coverage artifacts it produces are explicitly permitted.

    line 17

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

Triage the review feedback on the current branch's PR. Run this from the target PR's branch — the gh commands below operate on the current branch, so check out the PR's branch first (gh pr checkout <n>) if you're elsewhere.

SHARED-CHECKOUT REVIEW — EXPLICIT LEAD DIRECTION: this run is a shared-checkout review under explicit lead direction. If your role definition carries the fail-closed no-provisioned-worktree rule, it does not apply to this run. Do not edit repository files for the duration of this run: no hypothesis edits, no mutation testing, and nothing written into the tree under review. Read-only test execution and the incidental caches or coverage artifacts it produces are explicitly permitted. This invocation cannot perform the shared-tree protocol's lead safety-commit, and the no-repository-edit rule is what makes its absence tolerable — this direction is not the full shared-tree protocol.

PR

!gh pr view --json title,body,number,reviewDecision,mergeStateStatus 2>/dev/null || echo "pass a PR number"

Review comments

!gh pr view --comments 2>/dev/null

Checks

!gh pr checks 2>/dev/null

Diff

!gh pr diff 2>/dev/null

Task

Produce the triage plan per your pr-triage role: classify every comment, then give a single CLEAR TO MERGE / BLOCK recommendation. You adjudicate only — the author fixes; the lead merges.

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.