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
Most recently taken up by
- Hakktivist/claude-skillstheir own version, first seen Nov 2, 2026
- AlexisBalayre/claude-code-configtheir own version, first seen Oct 17, 2026
- AlexisBalayre/claude-code-power-configtheir own version, first seen Oct 17, 2026
- tstapler/dotfilestheir own version, first seen Oct 10, 2026
Who's talking about javierbrea/eslint-plugin-boundaries
- glimpse-hq/Glimpse“Bump the frontend group with 10 updates”GitHub · Nov 9, 2026 · 1 reactions
- JovieInc/Jovie“deps-dev(deps-dev): bump eslint-plugin-boundaries from 6.0.2 to 7.1.0”GitHub · Jul 27, 2026 · 1 reactions
- glimpse-hq/Glimpse“Bump the frontend group across 1 directory with 15 updates”GitHub · Jul 13, 2026 · 1 reactions
- glimpse-hq/Glimpse“Bump the frontend group with 6 updates”GitHub · Jul 6, 2026 · 1 reactions
- @waschlogic.com“Just came across github.com/javierbrea/e... yesterday. I'm sure its overkill for some, but allowing you to …”Bluesky · Apr 4, 2025 · 1 likes
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
- Nov 9, 2026Bump the frontend group with 10 updates — glimpse-hq/Glimpse1 reaction · 1 comment
- Jul 27, 2026deps-dev(deps-dev): bump eslint-plugin-boundaries from 6.0.2 to 7.1.0 — JovieInc/Jovie1 reaction · 5 comments
- Jul 13, 2026Bump the frontend group across 1 directory with 15 updates — glimpse-hq/Glimpse1 reaction · 2 comments
- Jul 6, 2026Bump the frontend group with 6 updates — glimpse-hq/Glimpse1 reaction · 2 comments
- Nov 10, 2026ci(deps-dev): bump the ci group with 2 updates — rmartz/ai-tools0 reactions
45 more on GitHub
- Nov 10, 2026chore(deps-dev): bump the lint-format group across 1 directory with 2 updates — Krkeek/auto-damm0 reactions
- Nov 9, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.4.0 to 7.4.2 in the dev-dependencies group — schallym/nestjs-messenger0 reactions · 1 comment
- Nov 9, 2026build(deps-dev): bump the dev-toolchain group across 1 directory with 9 updates — lorem-dev/ailoud0 reactions
- Nov 9, 2026chore(deps-dev): bump the lint group with 2 updates — lance1416/ctws0 reactions
- Nov 9, 2026chore(deps-dev): bump the ci group with 2 updates — rmartz/trip-planner0 reactions
- Nov 9, 2026build(deps-dev): Bump eslint-plugin-boundaries from 7.4.0 to 7.4.1 in the eslint group — withplumix/plumix0 reactions · 1 comment
- Nov 9, 2026chore(deps): Bump the dependencias group with 4 updates — Pavel0990/CERTIC-MAPS-SR0 reactions · 1 comment
- Nov 9, 2026chore(deps-dev): bump the development group with 3 updates — SongNoi/songnoi0 reactions
- Nov 9, 2026chore(deps): bump eslint-plugin-boundaries from 7.4.0 to 7.4.1 in the npm group — jiva-studio/numen0 reactions · 1 comment
- Nov 9, 2026build(deps-dev): bump the development-minor-patch group with 2 updates — VexaMail/vexa-insight0 reactions · 1 comment
- Nov 9, 2026chore(deps-dev)(deps-dev): bump the eslint group across 1 directory with 5 updates — Nks/opentranslate0 reactions · 1 comment
- Nov 9, 2026deps: bump the tooling group across 1 directory with 4 updates — loliman/shortbox-next0 reactions · 1 comment
- Nov 9, 2026chore(deps): bump the minor-and-patch group across 1 directory with 3 updates — minhhuy1201/guild-manager0 reactions · 2 comments
- Nov 8, 2026Bump eslint-plugin-boundaries from 7.4.0 to 7.4.2 — lotfi029/ta3lom_store_web0 reactions
- Nov 8, 2026chore(deps): bump the minor-and-patch group across 1 directory with 10 updates — MaksymovAndrew/portfolio0 reactions
- Nov 8, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.2.0 to 7.4.1 — gaboluque/blueprint0 reactions
- Nov 7, 2026chore(deps): Bump the dependencies group across 1 directory with 7 updates — stavkamil/blueprint0 reactions
- Nov 7, 2026chore(deps): Bump the minor-patch group with 5 updates — i-sato/ews-ai-agent0 reactions
- Nov 7, 2026chore(deps): bump the minor-and-patch group across 1 directory with 28 updates — Jundev66/CoreBiz0 reactions · 1 comment
- Nov 7, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.4.0 to 7.4.1 in the ci group — rmartz/pr-shepherd0 reactions
- Nov 7, 2026chore(deps-dev): Bump eslint-plugin-boundaries from 5.4.0 to 7.4.1 — WenYu0306/sage-spatial-agent-guidance-engine0 reactions
- Nov 7, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.2.1 to 7.4.1 — Keshav-Chaudhary/PlanCraftX0 reactions · 1 comment
- Nov 6, 2026Bump the minor-and-patch group across 3 directories with 13 updates — MaksymovAndrew/cooking-assistant0 reactions
- Nov 6, 2026chore(deps-dev): bump eslint-plugin-boundaries from 5.0.1 to 7.4.1 — dromeas-codereviewbench/retry_final__sentry__dromeas__PR93824__202609040 reactions
- Nov 5, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 10 updates — alexmorris10x/nextjs-saas-boilerplate0 reactions
- Nov 5, 2026Bump the npm group across 1 directory with 25 updates — mykola-blonskyi/spending0 reactions
- Nov 5, 2026chore(deps): Bump the npm-minor-patch group with 6 updates — bhavinvirani/running-coach0 reactions
- Nov 5, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.2.1 to 7.4.0 — dansilva-98/sistema-adrielli0 reactions
- Nov 5, 2026chore(deps): bump the npm group across 1 directory with 27 updates — Hidoni/lore-world-tracker0 reactions
- Nov 4, 2026chore(deps): bump the web-minor-patch group across 1 directory with 10 updates — GoLe-by-Colding/GoLe0 reactions
- Nov 4, 2026build(deps-dev): bump eslint-plugin-boundaries from 6.0.2 to 7.4.0 — pasaperez/react-frontend-template-ts0 reactions
- Nov 3, 2026Bump eslint-plugin-boundaries from 7.1.0 to 7.4.0 in /web — biloskurskyi/fast_api_posts0 reactions
- Nov 3, 2026chore: bump eslint-plugin-boundaries from 7.2.0 to 7.4.0 — Bori-github/tadaktadak0 reactions
- Nov 2, 2026chore(deps-dev): bump the lint-and-format group across 1 directory with 4 updates — juanpacj-wq/juancespedes.dev0 reactions
- Oct 30, 2026build(deps-dev): bump the lint group across 1 directory with 3 updates — ammarqureshi120/eventmanagement-frontend0 reactions
- Oct 28, 2026chore(deps): bump eslint-plugin-boundaries from 5.4.0 to 7.3.0 — gscalasanz/monorepo0 reactions · 1 comment
- Oct 26, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.2.0 to 7.2.1 — Revenantal/revenantal-website0 reactions
- Oct 26, 2026chore(deps): bump eslint-plugin-boundaries from 7.2.0 to 7.2.1 — cha2hyun/seed-design-starter0 reactions
- Oct 24, 2026Bump eslint-plugin-boundaries from 6.0.2 to 7.2.0 — adiikj/Argus0 reactions · 1 comment
- Oct 22, 2026chore(deps-dev): bump eslint-plugin-boundaries from 5.0.1 to 7.2.0 — dd-benchmarking/sentry__sentry__deputydev-v2-gpt-5-6__PR95633__202608120 reactions
- Oct 19, 2026Integrate `eslint-plugin-boundaries` — illia-m-b/ticket-guard-action0 reactions
- Oct 12, 2026chore(deps-dev): bump eslint-plugin-boundaries from 5.0.1 to 7.2.0 — Hewline-Ai/sentry__sentry__hew-r2__PR93824__202610120 reactions
- Oct 10, 2026chore(deps-dev): bump eslint-plugin-boundaries from 5.0.1 to 7.2.0 — peer-reviewer-bench/sentry__sentry-greptile__peer-reviewer__PR1__202610100 reactions
- Oct 8, 2026chore(deps-dev): bump eslint-plugin-boundaries from 5.0.1 to 7.2.0 — aether-bench/sentry__sentry__aether-r1__PR95633__202610070 reactions
- Oct 8, 2026chore(deps-dev): Bump eslint-plugin-boundaries from 6.0.2 to 7.3.0 — TheLightbulbCompany/lightbulb0 reactions · 4 comments
On Bluesky · 2
- Apr 4, 2025Just came across github.com/javierbrea/e... yesterday. I'm sure its overkill for some, but allowing you to setup custom rules for what… — @waschlogic.com1 likes and repost
- May 28, 2025With code organization and github.com/javierbrea/e... you can kinda get there. — @waschlogic.com0 likes and reposts · 1 reply
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- tstapler/dotfiles★ 8same name
- AlexisBalayre/claude-code-config★ 2same name
- AlexisBalayre/claude-code-power-config★ 2same name
- Hakktivist/claude-skills★ 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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- boundaries-architectSkill
- create-architectural-decision-recordSkill
- create-issueSkill
- create-prSkill
- documentation-writerSkill
- implement-changeSkill
- releaseSkill
- repo-architectureSkill
- review-prSkill
- unit-testingSkill
- write-planSkill
- writing-styleSkill
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
- Distinctive: line 60
A reply to a false comment gives the evidence and stops: no defense, and no thanks.
“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.
Files
Address review comments
A comment is a claim, never an order: nothing changes because of one before it is checked, whoever wrote it.
Procedure
- 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.
- Read every comment, as "Reading the comments" says: the threads on the code, the body of each review and the comments of the conversation.
- 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.
- Check each comment, as "Checking a comment" says, and give it its verdict. Change nothing yet.
- Ask the user about each comment of taste or of design, and each one that is not checkable, with what each choice costs.
- Fix the true ones through the
implement-changeskill, as one change with the comments as its tasks. A comment that reports wrong behavior first gets the test that fails because of it. - 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.
- Once they confirm, commit, push, and reply in each thread as "Replying" says, naming the commit.
- Bring the description of the pull request up to date with the
create-prskill when the fixes changed what it says. - 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
- 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.
- Check the claim on the last commit of the branch, by the way of "Checking a finding" of the
implement-changeskill that fits it. A claim about the published behavior is checked against the published version too. - Give it its verdict, with its evidence: the command and its output, or the lines that show it.
| Verdict | When | What follows |
| True | The check shows what the comment says | It is fixed |
| Partly true | Some of its claims hold | Those are fixed, and the reply tells the others apart |
| False | The check shows the opposite | Nothing changes |
| Taste or design | It is a preference, or it changes a decision of the design or of the plan | The user decides |
| Not checkable | Nothing here can show it true or false | The 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:
| Verdict | The reply holds |
| True | What changed and in which commit, in one or two sentences |
| Partly true | What changed, then the check that shows why the rest did not |
| False | The check and its result, so that the reviewer can run it again |
| Taste or design | What the user decided, and its reason |
| Not checkable | What 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.mdasks. 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.
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
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.

