comment-pr
Skill1 starsChanged 7 months agoMITView on GitHub
Draft and post a simple, human GitHub pull request comment after reviewing the PR context. Use when the user asks to comment on a PR, reply to a maintainer, follow up on review feedback, or post a short status/update message to a pull request. Always preview the exact comment and wait for explicit user approval before posting.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- niilohlin/skillstheir own version, first seen Nov 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- niilohlin/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 repository3 other files it gives its agents.
- create-prSkill
- lfx-proposalSkill
- lfx-research-architectSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 19 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈19
Distinctive · estimate
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 18
Never post a comment before showing the exact final comment to the user and getting explicit approval.
- Distinctive: line 29
If approval is unclear, ask again.
- Distinctive: line 35
If the user supplied a PR URL or number, use it directly.
- Distinctive: line 37
If the user did not specify a PR, find the current branch and associated PR:
- Distinctive: line 44
If no PR can be identified, stop and ask the user for the PR URL or number.
- Distinctive: line 48
Read enough context to understand what the comment is replying to:
- Distinctive: line 62
Use the PR's actual discussion.
- Distinctive: line 72
ask for confirmation on an approach
- Distinctive: line 76
If the intent is still ambiguous after reading the PR, ask the user one concise question before drafting.
- Distinctive: line 81
Write like a real open source contributor, not a bot.
- Distinctive: line 91
no AI/tool mentions
- Distinctive: line 96
no bullet list unless the comment genuinely needs multiple concrete items
- Distinctive: line 136
Do not run the posting command until the user approves.
- Distinctive: line 140
After approval, write the approved body to a temporary file and post it:
- Very specific: line 146
If gh pr comment is unavailable, use the GitHub API issue comment endpoint:
- Distinctive: line 152
After posting, print the PR URL and confirm that the comment was posted.
- Distinctive: line 156
If the PR is closed or merged, mention that in the preview and ask whether to still comment.
- Distinctive: line 158
If the comment contains claims about tests, verify those test commands actually ran or say only that the change was pushed.
- Distinctive: line 160
If a maintainer asked for something and the local diff does not show it was done, do not claim it is done.
- Distinctive: line 162
If there are multiple maintainers or multiple review threads, be clear which feedback the comment is addressing.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
comment-pr
Post a thoughtful GitHub pull request comment that sounds like the user wrote it.
The user may provide a PR URL, PR number, branch name, or a rough intent such as "reply to the maintainer", "say I fixed it", or "ask if this approach is okay".
Hard rule
Never post a comment before showing the exact final comment to the user and getting explicit approval.
Approval must be clear, such as:
yes post it
looks good, comment
go aheadIf approval is unclear, ask again. Do not infer approval from silence.
Workflow
1. Identify the PR
If the user supplied a PR URL or number, use it directly.
If the user did not specify a PR, find the current branch and associated PR:
git branch --show-current
gh pr view --json number,url,title,author,headRefName,baseRefName,stateIf no PR can be identified, stop and ask the user for the PR URL or number.
2. Read the PR context
Read enough context to understand what the comment is replying to:
gh pr view <pr> --json number,url,title,body,author,state,headRefName,baseRefName,comments,reviews,latestReviews,filesAlso inspect recent local work when it helps explain status:
git status --short
git log --oneline --decorate -n 8
git diff --statUse the PR's actual discussion. Do not invent maintainer feedback, test results, or project details.
3. Decide the comment intent
Classify the message before drafting:
- reply to review feedback
- say requested changes are done
- explain an implementation choice
- ask for confirmation on an approach
- share a blocker or request guidance
- give a short status update
If the intent is still ambiguous after reading the PR, ask the user one concise question before drafting.
4. Draft the comment
Write like a real open source contributor, not a bot.
Style rules:
- simple, direct, and human
- short, usually 1 to 4 sentences
- lowercase is okay where natural
- mild capitalization only: first word of a sentence and proper nouns
- no em dashes
- no corporate wording
- no AI/tool mentions
- no "implemented", "leveraged", "utilized", "streamlined", or similar inflated words
- no fake certainty
- no over-apology
- no signoff
- no bullet list unless the comment genuinely needs multiple concrete items
Prefer comments like:
thanks for the review. i pushed the change to keep this path behind the existing
validation, and added a test for the empty value case.i updated this based on your suggestion. the helper now returns early when there
is no configured backend, which keeps the current behavior for the default path.i'm not fully sure whether you want this handled here or closer to the caller. i
kept it here for now since this is where the existing validation already happens.Avoid comments like:
This PR has been updated to comprehensively address the feedback by leveraging
the existing validation infrastructure.5. Preview and wait
Show the user:
- the PR URL
- the exact comment body
- the command that will be used to post it
Then ask:
should i post this?Do not run the posting command until the user approves.
6. Post after approval
After approval, write the approved body to a temporary file and post it:
gh pr comment <pr> --body-file /tmp/comment-pr-body.mdIf gh pr comment is unavailable, use the GitHub API issue comment endpoint:
gh api repos/<owner>/<repo>/issues/<pr-number>/comments --method POST --field body="$(cat /tmp/comment-pr-body.md)"After posting, print the PR URL and confirm that the comment was posted.
Safety checks
- If the PR is closed or merged, mention that in the preview and ask whether to still comment.
- If the comment contains claims about tests, verify those test commands actually ran or say only that the change was pushed.
- If a maintainer asked for something and the local diff does not show it was done, do not claim it is done.
- If there are multiple maintainers or multiple review threads, be clear which feedback the comment is addressing.
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.

