agentleFS
aaronbrethorstaaronbrethorst/claude-skills/pr-sweep/SKILL.md

pr-sweep

Skill4 starsChanged 10 months agoNo licenceView on GitHub

Review and disposition a batch of open GitHub pull requests in one pass: run a rigorous /code-review on each, post the findings as a PR comment, and report a merge recommendation for every PR — then, when the user has explicitly asked for it, execute the dispositions (approve+merge the ready ones, request changes on the rest) with kind-but-firm maintainer feedback. Use this whenever the user wants to work through one or more open PRs as a queue: "go through all the open PRs from @author", "triage the open PR queue", "review these PRs" with a pasted list of numbers/URLs, "review Tarun's PRs and merge the ready ones", "clear out the PR backlog". The skill has two modes: it always reviews and recommends; it only merges/approves/requests-changes autonomously when the user's own words ask for the action (merge, land, ship, close out, "merge the good ones") — otherwise it presents dispositions and asks first. A "is this PR ready to merge?" question with no action requested is a verdict request — answer it (or use aaron-pr-review), don't execute anything.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 9 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.