agentleFS
learntocloudlearntocloud/learn-to-cloud-app/.github/skills/review-pr-comments/SKILL.md

review-pr-comments

Skill1.1k starsChanged 59 days agoMITView on GitHub

Triage and address top-level and inline comments on the active pull request. Use for "review PR comments", "address review comments", or "handle PR feedback".

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Use gh to identify the pull request for the current branch and fetch issue comments, reviews, inline comments, and unresolved review …

    line 8
  2. Distinctive:

    Ask for the user's decision one comment at a time.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 6 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.

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

Review Pull Request Comments

Use gh to identify the pull request for the current branch and fetch issue comments, reviews, inline comments, and unresolved review threads.

  1. Present each actionable comment once with its author, location, summary, and recommendation: accept, iterate, reject, or answer only.
  2. Ask for the user's decision one comment at a time. Do not edit before that comment's decision.
  3. For accepted or iterated feedback, make and validate the change. For rejected feedback, record the technical reason.
  4. Reply directly to the originating comment with the outcome and commit SHA when available. Resolve an inline thread only after its outcome is delivered.

Ignore superseded comments and bot summaries that contain no actionable feedback. Never claim a comment is addressed before the change is present and validated.

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.