leaving-pr-comments — Claude Code skill: what it does, how to install
leaving-pr-comments is a Claude Code skill that formats GitHub pull request comments with model and user attribution.
MIT 1,300 installs ★ 4,278 updated 2026-11-11
npx skills add t3dotgg/tstack --skill leaving-pr-comments -a claude-codeWhat leaving-pr-comments does
The skill runs when leaving comments on GitHub. Every agent response is prefixed with a note callout showing the model and user name, or harness name if the model is unexposed.
Before posting, the text is checked for secrets and private data. The reply keeps a direct style leading with the conclusion.
Before publishing comments, the entire text and attachments are scanned for private details and secrets.
What it helps with
- format a pull request comment with model attribution
- scan review comments for secrets before posting
- reply to reviewer feedback with robot emoji prefix
- post direct review notes without filler text
Example prompts for the agent
- Leave a comment on this pull request using proper attribution
- Reply to this review thread as the agent
- Check this draft comment for secrets before posting
How to install leaving-pr-comments
1Skills CLI (Vercel)
npx skills add t3dotgg/tstack --skill leaving-pr-comments -a claude-code2Manually: put the files in place
~/.claude/skills/leaving-pr-comments/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/leaving-pr-comments/
1Skills CLI (Vercel)
npx skills add t3dotgg/tstack --skill leaving-pr-comments -a codex2Manually: put the files in place
.agents/skills/leaving-pr-comments/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add t3dotgg/tstack --skill leaving-pr-comments -a cursor2Manually: put the files in place
.cursor/skills/leaving-pr-comments/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install t3dotgg/tstack skills/leaving-pr-comments2Manually: put the files in place
.github/skills/leaving-pr-comments/SKILL.md1Skills CLI (Vercel)
npx skills add t3dotgg/tstack --skill leaving-pr-comments -a gemini-cli2Platform CLI
gemini skills install https://github.com/t3dotgg/tstack --path skills/leaving-pr-commentsManually: put the files in place
.devin/skills/leaving-pr-comments/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add t3dotgg/tstack --skill leaving-pr-comments -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about leaving-pr-comments
How to install leaving-pr-comments in Claude Code?
Run npx skills add t3dotgg/tstack --skill leaving-pr-comments -a claude-code and check ~/.claude/skills/leaving-pr-comments/SKILL.md.
What does leaving-pr-comments do?
It prepends GitHub comments with a standardized Markdown note containing model and user details.
When is the skill triggered?
It applies to pull request comments, inline review replies, and feedback responses on GitHub.
Source text
SKILL.md · MIT
--- name: leaving-pr-comments description: Use whenever leaving comments on GitHub. --- # Leaving PR Comments Prefix every agent-authored comment left on the user's behalf with this GitHub note callout: ```md > [!NOTE] > 🤖 **<model> responding on behalf of <user>** Actual comment starts here. ``` Use the verified public name of the model that wrote the comment, and the user's name or GitHub login. If the harness does not expose a model name, use the harness name. Do not guess. Before posting, check the entire comment, including quoted text and attachments, for secrets and private details. Keep the attribution inside the note and the actual reply outside it. The context line must start with the robot emoji. Do not add a horizontal rule, Setext underline, heading, signature footer, or a second attribution. Apply this format to top-level PR comments, inline review comments, replies to bots or reviewers, and written explanations used before resolving or dismissing feedback. Do not add it to PR descriptions, commit messages, or text the user explicitly asked to post verbatim without attribution. Write the comment itself in a direct style: - Lead with the conclusion. - Cite the relevant code, behavior, check, or reproduction. - Keep it concise and avoid filler, canned thanks, or status narration. - Distinguish verified facts from judgment. Preview the final Markdown before posting so quoting and blank lines render as shown. After posting, verify that GitHub returned the comment or review URL. Resolve a review thread only after its response was posted successfully.
© t3dotgg · MIT · t3dotgg/tstack