agentleFS
PinWPinW/whisper-key-local/.agents/skills/triage-pr/SKILL.md

triage-pr

Skill203 starsChanged 50 days agoMITView on GitHub

Triage GitHub PR review comments one by one

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. block/proto-fleet★ 57same name
    2. syamaner/roastpilot-agent★ 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.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Ask user whether to:

    line 19
  2. Distinctive:

    After all comments are triaged, summarize what was changed and what was skipped

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 review comments from a GitHub PR. Argument: PR number or URL.

Steps

  1. Fetch the PR review comments using gh pr view <number> --comments and gh api repos/{owner}/{repo}/pulls/{number}/comments
  2. Parse out individual review suggestions/comments (skip resolved ones)
  3. For each comment, present it to the user one at a time with:
    • The file and line(s) referenced
      • The reviewer's comment text
      • Any suggested code change
    • For each comment, analyze:
      • Is it real? — Is the reviewer's observation factually correct? (Check the code to verify)
      • Do we care? — Even if correct, is it worth acting on?
  4. Ask user whether to:
    • Make the fix
    • Move to the next comment
  5. After all comments are triaged, summarize what was changed and what was skipped

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.