leaving-pr-comments
Use when posting any comment, review reply, or dismissal reason on GitHub on the user's behalf.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- leaving-pr-comments
- metadata
- { "upstream": "t3dotgg/tstack" }
- description
- Use when posting any comment, review reply, or dismissal reason on GitHub on the user's behalf.
02 资源文件 1
- 许可证LICENSE1.0 KB
03 SKILL.md 正文
Leaving PR Comments
Write every comment in a direct style:
- Lead with the conclusion.
- Cite the relevant code, behavior, check, or reproduction.
- Separate verified facts from judgment.
Before posting, check the whole comment, quoted text and attachments included, for secrets and private details. After posting, confirm GitHub returned the comment or review URL. Resolve a review thread only after its reply posted.
04 同仓库更多 Skills
tdd
Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
task-observer
Use when the user asks to log a skill observation, review the observation log, run a skill review, or discuss skill taxonomy, or says "One Skill to Rule Them All". Not for a subagent dispatched by a session already running it: that subagent puts its findings in its report.
software-factory
Use when designing a software factory, choosing the services it plugs into, or defining the tasks it runs.
no-comments
Use when the user wants scoped code comments reviewed, accepted findings fixed, or claimed constraints encoded as enforceable checks.
no-ai-slop
Use when the user wants a draft edited to read clearer, more direct, more opinionated, or less AI-sounding, wants AI-slop patterns flagged without a rewrite, or asks whether writing reads as AI.
merged
Use when a pull request has merged and the local repo should be cleaned up for the next piece of work, whether the user says so, runs /merged, or wait_merged.sh exits 0.