leaving-pr-comments
Use whenever leaving comments on GitHub.
- License 许可
- MIT
- 所属仓库
- saphitv/skills
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- leaving-pr-comments
- description
- Use whenever leaving comments on GitHub.
02 资源文件 2
- 参考文档agents/openai.yaml198 B
- 许可证LICENSE1.0 KB
03 SKILL.md 正文
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.
04 同仓库更多 Skills
takeover
Take over existing work. Use when the user asks to take over a PR, branch, or agent thread, or requests a takeover.
statechart
Check a TLA+ model of a system that moves between states, such as a product flow, a protocol, or a service, and draw it as a Mermaid statechart. The report gives the shortest path to each state that breaks a rule. Use for /statechart, or to show a bug as a path through states.
sol-loop
Use when the user says "sol loop".
security-audit-testing
Experimental Cloudflare security-audit trial for security questions, focused vulnerability reviews, codebase audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
retro
Conduct a retrospective on a coding session.
modernize
For getting old prs up to date. Use when asked to rebase a pr or "modernize".