pr-comment-fixer
Fix GitHub PR review comments for a watched /dev-loop PR. Use when the poller launches a fixer, checks failed, or the user says address PR comments. Use gh, not GitHub MCP.
- License 许可
- MIT
- 最近更新
- 2026-09-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- pr-comment-fixer
- description
- Fix GitHub PR review comments for a watched /dev-loop PR. Use when the poller launches a fixer, checks failed, or the user says address PR comments. Use gh, not GitHub MCP.
03 SKILL.md 正文
PR comment fixer
Input: pr-comments.md in the run dir (~/.config/dev-conductor/dev-loop/runs/KEY/).
- Read comments. Classify each: simple (rename, import, typo, obvious test) vs needs reasoning (design, API shape, security).
Ignore comments that only restate the code. If a comment is factually wrong about the diff, say so in the
gh pr commentnote. - Simple → implement with
tdd(failing test if behavior changes, then code). Do not weaken tests except compile/syntax/simple IO or a spec contradiction. - Needs reasoning → decide in this session, then implement. Do not bounce to another agent for nits.
- Stay on the feature branch. Conventional commit (
feat/fix+ Jira key). Never commit tomain/master. Never force-push. Never rewrite pushed history. gh pr comment N --body "..."a short note.gh pr edit --add-reviewer/ re-request review withgh.- Write
STAGE_DONEin the run dir.
Do not use GitHub MCP or Jira MCP.
If a review comment corrects a durable agent convention (handshake, isolation, secrets, stack law), load agent-memory and update one relevant file before STAGE_DONE. Skip one-ticket nits.
04 同仓库更多 Skills
verify-before-done
Use before claiming work is complete, fixed, or passing, and before commit or PR. Run the proof command in this turn.
token-playbook
Token budget for Claude Code. Use when shrinking CLAUDE.md, choosing skills vs rules vs MCP, compressing tool output, or cutting always-on context.
test-writer
Write failing tests from a technical spec and public contracts only. Use in /dev-loop test-writer stage. Do not read implementation sources or write production code.
tdd
Use when implementing a feature or bugfix, before writing production code. Test first, watch it fail, then implement. Vertical slices at public seams.
systematic-debugging
Use when hitting a bug, test failure, or unexpected behavior, before proposing a fix. Find root cause first.
story-spec
Turn a Jira story into a technical spec via grill. Use in the spec stage of /dev-loop. Do not implement.