agentleFS
Sign inStart free
luisgui1757luisgui1757/sentinel/skills/leaving-pr-comments/SKILL.md

leaving-pr-comments

Skill0 starsChanged 10 days agoMITView on GitHub

Use whenever leaving comments on a pull request or merge request, on any forge.

9 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use takeover.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • assisjpSkill

    takeover

    Take over an existing branch, pull request, worktree, or agent handoff while preserving the original goal, contributor credit, and concurrent work. Use when the user asks to take over, finish, rescue, or continue someone else's implementation. Do not use to replace a clear request to start new work.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 6 are common, 0 are distinctive, and 1 is very specific to this project.

  • 6

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    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
  1. Very specific:

    Keep the > [!NOTE] line only on a forge that shows it as a note box, such as GitHub.

    line 18
  2. Common:

    Use the verified public name of the model that wrote the comment, and the user's name or forge login.

    line 21
  3. Common:

    If the harness does not expose a model name, use the harness name.

    line 24
  4. Common:

    Before posting, check the entire comment, including quoted text and attachments, for secrets and private details.

    line 26
  5. Common:

    Keep the attribution inside the quote and the actual reply outside it.

    line 29
  6. Common:

    Write the comment itself in a direct style:

    line 38
  7. Common:

    Keep it concise and avoid filler, canned thanks, or status narration.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

Leaving PR Comments

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

> [!NOTE]
> 🤖 **<model> responding on behalf of <user>**

Actual comment starts here.

Keep the > [!NOTE] line only on a forge that shows it as a note box, such as GitHub. On other forges, remove it and keep the robot line as a plain quote.

Use the verified public name of the model that wrote the comment, and the user's name or forge 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 quote 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 the forge returned the new comment, with its URL or ID. Resolve a review thread only after its response was posted successfully.

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