aicodekingaicodeking/deepseek-stack/skills/ds-pr-comments/SKILL.md

ds-pr-comments

Skill80 starsChanged 15 days agoMITView on GitHub

Formats and posts GitHub comments written by an agent on the user's behalf, with clear attribution and no leaked secrets. Use whenever you post a PR comment, review reply or dismissal reason, or on /ds-pr-comments.

In this repository28 other files it gives its agents.
- ds-adoptSkill
- ds-best-of-nSkill
- ds-blast-radiusSkill
- ds-blueprintSkill
- ds-catchupSkill
- ds-context-resetSkill
- ds-design-auditSkill
- ds-designSkill
- ds-explainSkill
- ds-helpSkill
- ds-jurySkill
- ds-ledgerSkill
- ds-lessonsSkill
- ds-modeSkill
- ds-plan-loopSkill
- ds-principlesSkill
- ds-prSkill
- ds-readySkill
- ds-review-loopSkill
- ds-reviveSkill
- ds-sharpenSkill
- ds-shipSkill
- ds-swarmSkill
- ds-tddSkill
- ds-unslopSkill
- ds-unstickSkill
- ds-verify-loopSkill
- ds-watch-prSkill

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
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:
Write the reply. Lead with the conclusion.
line 10
Distinctive:
Put this note at the top, with the reply below it:
line 11
Distinctive:
Use the model name the harness reports.
line 20
Distinctive:
Use the note on top-level comments, inline review comments, replies to bots and people, and dismissal reasons.
line 34
Distinctive:
Do not use it in PR descriptions, commit messages or text the user asked to post word for word.
line 35
Distinctive:
No thanks, filler or status updates such as "still working on it".
line 37
Distinctive:
Never guess the model name.
line 38

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Make every agent-written comment easy to spot, short and safe to publish.

Steps

Write the reply. Lead with the conclusion. Cite the code line, check, test or reproduction that supports it. Mark what you verified and what is your opinion.
Put this note at the top, with the reply below it:
```
> [!NOTE]
> **<model> responding on behalf of <user>**

Reply text starts here.
```
Use the model name the harness reports. If it reports none, use the harness name. Use the user's name or GitHub login.
Scan the full comment, including quotes and attachments, for secrets, tokens, private paths and personal data. Remove them.
Preview the final Markdown. Confirm the note and the reply render as two separate blocks.
Post the comment.
Confirm GitHub returned the comment or review URL. Print it.
Resolve a review thread only after its reply posted.

Stop when

GitHub returned a URL for each comment you meant to post.
A post fails twice. Report the error and do not resolve the thread.

Rules

Use the note on top-level comments, inline review comments, replies to bots and people, and dismissal reasons.
Do not use it in PR descriptions, commit messages or text the user asked to post word for word.
One attribution only. No signature, footer, heading or horizontal rule.
No thanks, filler or status updates such as "still working on it".
Never guess the model name.

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.

Check your setup, free