mcpField
L
leaving-pr-comments

leaving-pr-comments

github.com/t3dotggDevelopment2.2k274 installsUpdated 1d ago
Repository

About leaving-pr-comments

A skill for agents that write GitHub pull-request comments on a user's behalf. It specifies a consistent attribution note, privacy checks, concise response style, and verification after posting.

Key features

  1. 01Required attribution note format
  2. 02Secret and privacy checks
  3. 03Concise comment guidance
  4. 04Preview Markdown before posting
  5. 05Verify posted comment and URL

Use cases

  1. 01Writing a top-level PR comment
  2. 02Replying to reviewers or bots
  3. 03Explaining a review-thread resolution

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/t3dotgg/tstack --skill leaving-pr-comments

After installing, type/leaving-pr-commentsin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Leaving PR Comments

Prefix every agent-authored comment left on the user's behalf with this GitHub note callout:

> [!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.

Comments

Markdown supported