t3dotgg/tstack

leaving-pr-comments

Use whenever leaving comments on GitHub.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/t3dotgg/tstack --skill leaving-pr-comments

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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.

aus demselben Repository

Weitere Skills

Alle Skills