address-comments
Skill246 starsChanged 5 months agoMITView on GitHub
Apply CLAUDE:-prefixed comments from a pull request
3 other projects use a version of this.
Adopted by
Most recently taken up by
- lucastosetto/dev-skillstheir own version, first seen Oct 15, 2026
- bryce-evans/claude-skillstheir own version, first seen Oct 13, 2026
- oleg-chibikov/agent-skillstheir own version, first seen Sep 16, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- oleg-chibikov/agent-skills★ 1same name
- bryce-evans/claude-skills★ 0same name
- lucastosetto/dev-skills★ 0same 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 repository23 other files it gives its agents.
- openhost-agent/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- auto-qa-changesSkill
- auto-qa-iphoneSkill
- batch-claude-runnerSkill
- code-review-checklistSkill
- cut-releaseSkill
- debug-integration-testSkill
- frontend-design-tokensSkill
- manually-qa-branchSkill
- measure-react-rendersSkill
- openhost-frontend-previewSkill
- openhost-sculptorSkill
- post-pr-to-slackSkill
- profile-sculptor-backendSkill
- promote-releaseSkill
- run-integration-testSkill
- storybook-screenshotSkill
- update-help-docsSkill
- update-review-rulesSkill
- update-specsSkill
- write-integration-testSkill
- write-release-notesSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
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
- Distinctive: line 20
Read the referenced file (if it's an inline comment on a specific line)
- Distinctive: line 25
Do NOT push any code
- Distinctive: line 26
Do NOT reply to the comments on GitHub
- Distinctive: line 27
Only make local changes
- Very specific: line 36
If a PR number was provided, use it.
- Distinctive: line 46
If it's an inline comment, note the file path and line number for context
- Distinctive: line 47
Read the relevant file(s)
“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.
Files
Apply PR Comments
Fetch comments from a pull request and apply all comments that are prefixed with "CLAUDE:".
Instructions
- Fetch the PR's comments via
gh(see "Fetching comments" below). If a PR number is provided, use it. Otherwise, resolve the current branch's PR withgh pr view --json number. - Parse the output to find all comments (including discussion notes and inline code comments) that start with "CLAUDE:" (case-insensitive).
- For each CLAUDE: comment found:
- Read the referenced file (if it's an inline comment on a specific line)
- Understand what change is being requested
- Apply the requested change to the local codebase
- Important restrictions:
- Do NOT push any code
- Do NOT reply to the comments on GitHub
- Only make local changes
Fetching comments
Fetch the PR's comments — both inline review comments and general discussion — with gh:
- Inline review comments:
gh api --paginate "repos/{owner}/{repo}/pulls/<N>/comments"— each has.body,.path, and.line(or.original_line).ghsubstitutes{owner}/{repo}for the current repo. - General discussion:
gh api --paginate "repos/{owner}/{repo}/issues/<N>/comments".
If a PR number was provided, use it; otherwise resolve the current branch's PR with gh pr view --json number.
Important: the comment JSON can be large and may get truncated — save it to a temp file first, then parse with jq in a separate command (not chained with &&) to avoid shell-parsing issues with the jq expression.
From the fetched comments, select those whose body starts with "CLAUDE:" (case-insensitive). For each, capture the body and — for inline comments — the file path and line. GitHub's REST comments have no resolved flag, so rely on the diff to see what's already done.
Applying Changes
For each CLAUDE: comment:
- Extract the instruction (everything after "CLAUDE:")
- If it's an inline comment, note the file path and line number for context
- Read the relevant file(s)
- Apply the requested change
- Move on to the next comment
Summarize all changes made at the end.
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.

