AGENT SKILL

ds-pr-comments

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.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
ds-pr-comments
description
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.

03 SKILL.md 正文

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

Steps

  1. 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.

  2. 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.

  3. Scan the full comment, including quotes and attachments, for secrets, tokens, private paths and personal data. Remove them.

  4. Preview the final Markdown. Confirm the note and the reply render as two separate blocks.

  5. Post the comment.

  6. Confirm GitHub returned the comment or review URL. Print it.

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

Greeneek working contract

This skill is installed in the Greeneek repository. Where a step below conflicts with these rules, these rules win.

  • Restate the goal in one line, read the real files before editing, and work on main in small vertical slices. Preserve uncommitted and concurrent work; never reset, force-push, or overwrite another session's changes.
  • Evidence before "done": run the real check and record the exact command and its output. Never weaken a test, add a blind retry, raise a timeout without a diagnosed cause, or delete a failing assertion to get green.
  • Agent waves never commit, push, tag, or publish. No npm auto-publish on main; release tags are immutable and Item 8 stays last.
  • Live model lanes stay BLOCKED without GREENEEK_API_KEY; mocked coverage is never reported as real-CLI verification.
  • Registrations are effects, ESM everywhere, and misconfiguration fails at the earliest resolvable point.
  • Source of truth: .agents/notes/proposed/process/2026-11-01-v0.3.9-master-release-plan.md. Append evidence to its Execution ledger and keep its Resume State current in the same commit as the change.

Greeneek-specific override

Never paste credentials, absolute personal paths, .env contents, or untracked scratch into a comment. Cite the exact command and its result, and separate what was verified from what is an opinion.

04 同仓库更多 Skills