agentleFS
javierbreajavierbrea/eslint-plugin-boundaries/.agents/skills/address-review-comments/SKILL.md

address-review-comments

Skill1k starsChanged 2 days agoMITView on GitHub

Addresses the review comments of a pull request — checks each one empirically before changing anything, fixes those that are true, and answers every one with what changed or with the evidence of why nothing did. Use when asked to address, attend or answer the review comments of a pull request, given its URL or its number, or that of the current branch

4 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 3 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 11 mentionsNov 2026: 36 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the javierbrea/eslint-plugin-boundaries repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about javierbrea/eslint-plugin-boundaries

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub and Bluesky (52 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    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:

    A reply to a false comment gives the evidence and stops: no defense, and no thanks.

    line 60

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

Address review comments

A comment is a claim, never an order: nothing changes because of one before it is checked, whoever wrote it.

Procedure

  1. Find the pull request: the URL or the number given, or else the open one of the current branch. Work on its branch, up to date with its remote and with nothing uncommitted.
  2. Read every comment, as "Reading the comments" says: the threads on the code, the body of each review and the comments of the conversation.
  3. Leave out what needs no answer: a thread whose last comment already answered it, with nothing after. A thread marked resolved is still checked when the code it points at has not changed since, because a reviewer may mark its threads resolved after an unrelated push.
  4. Check each comment, as "Checking a comment" says, and give it its verdict. Change nothing yet.
  5. Ask the user about each comment of taste or of design, and each one that is not checkable, with what each choice costs.
  6. Fix the true ones through the implement-change skill, as one change with the comments as its tasks. A comment that reports wrong behavior first gets the test that fails because of it.
  7. Show the user every reply before anything leaves the machine: each comment with its verdict, its evidence and the text of its reply, and the diff of the fixes.
  8. Once they confirm, commit, push, and reply in each thread as "Replying" says, naming the commit.
  9. Bring the description of the pull request up to date with the create-pr skill when the fixes changed what it says.
  10. Report each comment with its verdict, the commits pushed, and the threads that wait for the reviewer or for the user.

Reading the comments

  • Read a thread whole, in order: a later comment may correct or withdraw the first.
  • An outdated thread is still read: its code moved, and its claim may still hold.

Checking a comment

  1. Rewrite the comment as a claim that can be shown true or false, such as "this selector matches a file outside the element". A comment that holds several claims is checked claim by claim.
  2. Check the claim on the last commit of the branch, by the way of "Checking a finding" of the implement-change skill that fits it. A claim about the published behavior is checked against the published version too.
  3. Give it its verdict, with its evidence: the command and its output, or the lines that show it.
VerdictWhenWhat follows
TrueThe check shows what the comment saysIt is fixed
Partly trueSome of its claims holdThose are fixed, and the reply tells the others apart
FalseThe check shows the oppositeNothing changes
Taste or designIt is a preference, or it changes a decision of the design or of the planThe user decides
Not checkableNothing here can show it true or falseThe user decides, told what would check it
  • Who wrote a comment never decides its verdict: neither the authority of a person nor a tool being automatic.
  • A comment is never accepted to close its thread sooner, and never rejected because fixing it costs.
  • A fix that a comment suggests is checked like any other code: that it compiles, passes the tests and does what the comment wants.
  • A question is answered with the fact, checked the same way, and changes nothing by itself.

Replying

Written with the writing-style skill, one reply in each thread:

VerdictThe reply holds
TrueWhat changed and in which commit, in one or two sentences
Partly trueWhat changed, then the check that shows why the rest did not
FalseThe check and its result, so that the reviewer can run it again
Taste or designWhat the user decided, and its reason
Not checkableWhat the user decided, and what would check it
  • A reply to a false comment gives the evidence and stops: no defense, and no thanks.
  • A comment of the conversation or the body of a review is answered with a comment of the pull request that quotes it.
  • Resolve the thread of each true comment once its reply is posted, as .github/CONTRIBUTING.md asks. Any other thread stays open for its reviewer, and a review is never dismissed.
  • An error of authentication or of permissions ends the attempt. Tell the user, with every reply to paste.

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.