github-pr-comment
Skill97 starsChanged 32 days agoApache-2.0View on GitHub
Post one exact GitHub pull-request comment through the GitHub connector, with retry safety and independent readback.
In this repository94 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- runxSkill
- adopt-skillSkill
- agencySkill
- answer-from-docsSkill
- attention-reviewSkill
- audit-receiptSkill
- brand-voiceSkill
- business-opsSkill
- chargeSkill
- chief-of-staffSkill
- cold-outreachSkill
- content-pipelineSkill
- contract-drafterSkill
- conversation-replySkill
- conversation-reviewSkill
- crm-cleanupSkill
- cve-auditSkill
- data-storeSkill
- data-subject-requestSkill
- deep-researchSkill
- diagnose-skill-runSkill
- dispute-respondSkill
- ecosystem-briefSkill
- extractSkill
- ghostwriteSkill
- github-pr-reviewSkill
- github-syncSkill
- google-analyticsSkill
- google-calendarSkill
- google-search-consoleSkill
- governed-outboundSkill
- helpdeskSkill
- incident-commanderSkill
- issue-intakeSkill
- issue-to-prSkill
- issue-triageSkill
- knowledge-routerSkill
- lead-enrichmentSkill
- lead-qualifySkill
- least-privilegeSkill
- ledgerSkill
- list-hygiene-judgeSkill
- marketplace-invokeSkill
- meeting-followupSkill
- mock-chargeSkill
- mock-paySkill
- mock-refundSkill
- moltbookSkill
- n8n-handoffSkill
- nitrosendSkill
- nws-weather-forecastSkill
- open-meteo-weather-forecastSkill
- operator-inboxSkill
- ops-deskSkill
- organic-growthSkill
- policy-authorSkill
- postmortem-makerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- could be automatic: a setting could enforce it
- Very specific: line 13
Use it after a review workflow has produced final wording and the operator wants that exact note posted.
- Distinctive: line 35
Stop when repository, pull-request number, body, or idempotency key is missing or changes after admission.
- Distinctive: line 40
Do not treat mutation acceptance without an independent comment read whose id and body match as final readback.
- Distinctive: line 42
Never merge, close, label, or otherwise mutate the pull request beyond the exact comment.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
GitHub PR Comment
Post one bounded review comment to one known GitHub pull request. The skill is deliberately narrower than a general GitHub operator: it binds the exact repository, pull request, and comment body to a scoped provider operation, and closes only when provider evidence identifies and reads back the created note.
Use it after a review workflow has produced final wording and the operator wants
that exact note posted. Use issue-triage for analysis and drafting, and a
broader GitHub skill for other resource types. This skill never merges a pull
request; comment authority cannot be promoted into merge authority.
How it works
- Supply
owner/name, the exact pull-request number, exact comment body, and a stable idempotency key for that body. - The default
postrunner callsgithub/comments.createonce with the exact body, under the GitHub instance selected here: the signed-inghsession or a stored token. - The runtime records GitHub's acknowledgement, reads the comment back by its id, and completes only when the read-back id and body match the approved comment.
The separate merge-refused runner asks for github/pullrequest.merge under
the same comment grant. It is an executable authority test: the merge request
must seal as policy denied, never as a backdoor merge path.
Stop conditions
- Stop when repository, pull-request number, body, or idempotency key is missing or changes after admission.
- Refuse a provider grant that does not resolve uniquely to
pr.comment. - Refuse when no GitHub instance is selected, or the selected one cannot comment; the skill never handles a raw token.
- Do not treat mutation acceptance without an independent comment read whose id and body match as final readback.
- Never merge, close, label, or otherwise mutate the pull request beyond the exact comment.
Example
An operator invokes post with “Please add the missing recovery fixture” for
PR 42 under a pr.comment grant. The skill posts exactly that body under the
stable retry key and seals the returned comment id. Changing the body changes
the operation identity. Attempting to reuse the comment grant for merge is
denied before GitHub mutation.
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.