菜单
Address the owner's GitHub review comments on an issue's PR — pull the comments, fix them in the issue's worktree, push, and reply per review thread. Fourth stage of the flow delivery workflow (see docs/workflow.md). Owner-invoked when they return after reviewing; never polls.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Activate a groomed GitHub issue for development — create its git worktree and branch, delegate the design to the architect agent (consulting a domain-expert agent for any architectural/data-model decisions), run OpenSpec explore+propose to produce a committed spec, and stop for the owner's spec approval. Second stage of the flow delivery workflow (see docs/workflow.md). This is the human approval seam; it never implements.
Finalize a merged issue — sync the OpenSpec change's delta specs into the canonical specs, archive the change, remove its git worktree, and close the GitHub issue. Final stage of the flow delivery workflow (see docs/workflow.md). Runs after the owner squash-merges the PR in GitHub; it never merges.
Implement an approved issue — run the background subagent team (tdd-developer → 5-lens review panel → fix loop → build-engineer → docs polish) via a Workflow script in the issue's worktree, then push the branch and open a PR. Third stage of the flow delivery workflow (see docs/workflow.md). Requires the owner to have approved the committed spec first. Invoking this skill is the explicit opt-in to multi-agent Workflow orchestration.
Report status across all in-flight delivery pipelines — every issue by lifecycle label with its priority, stage, worktree, and PR state — and highlight what's next and what's blocked on the owner. Use when the owner asks 'where do things stand' or 'what should I work on'. Part of the flow delivery workflow (see docs/workflow.md).
Pull the branch's latest CI test failures into the issue's local flagged set — download the spec-flow-failures artifact from the most recent CI run and append the failing test ids to .spec-flow/flagged-tests in the worktree, so the local loop runs them for the rest of the branch. Part of the flow delivery workflow (see docs/workflow.md, "Test tiering"). Owner-invoked when CI reports red; never polls.
One-time migration that splits a repo's existing test suite into the fast unit tier and the slow integration tier the flow test-tiering model assumes — classify tests by evidence (container/I-O/timing) and let the compiler + test timings arbitrate, physically separate them (Gradle source set + classpath scoping, or Rust src/ vs tests/ + nextest profiles), wire the CI failures artifact, and open a PR. Run once per repo, before test tiering applies. See docs/workflow.md ("Test tiering"). Never merges.
| name | address |
| description | Address the owner's GitHub review comments on an issue's PR — pull the comments, fix them in the issue's worktree, push, and reply per review thread. Fourth stage of the flow delivery workflow (see docs/workflow.md). Owner-invoked when they return after reviewing; never polls. |
| argument-hint | ["issue number","or its PR number"] |
You are the PM/lead in the main session. The owner reviewed the PR for issue #N in GitHub
and left comments. Pull them, fix them in the worktree, push, and reply to each thread. This
is owner-invoked (run it when you're back) — there is no polling.
Input: an issue number #N (or its PR number). Worktree .claude/worktrees/issue-<N>-<slug>,
branch issue-<N>-<slug>. If <slug> isn't already known from context, recover it with
git worktree list | grep "issue-<N>-" or gh pr list --search "head:issue-<N>-" --json headRefName.
Find the PR and fetch review comments.
gh pr list --head issue-<N>-<slug> --json number,url
# Review threads (line comments) + their bodies:
gh api repos/{owner}/{repo}/pulls/<PR>/comments --paginate
# Top-level review summaries:
gh pr view <PR> --json reviews,comments
If there are no new comments since the last address pass, say so and stop — don't invent work.
Mark addressing.
gh issue edit <N> --remove-label status:in-review --add-label status:addressing
Fix in the worktree. Dispatch a fix agent (background Agent) with the worktree path
and the collected comments. Choose the agent by the nature of the comments:
tdd-developer (test-first);reviewer to re-check after fixes, or
build-engineer for build/lint/format.
Instruct it to make focused commits, keep the unit tier (plus the branch's
.spec-flow/flagged-tests, if any) green locally as its gate — never the full/integration
suite, which is CI's gate — and never push or touch main. See Test tiering (unit /
integration) in docs/workflow.md.Push the branch (outward-facing — done here, narrated):
git -C <worktree> push origin issue-<N>-<slug>
Reply per thread. For each review comment you addressed, post a reply noting the commit that resolved it:
gh api repos/{owner}/{repo}/pulls/<PR>/comments/<comment-id>/replies \
-f body="Addressed in <short-sha>: <one line>."
Back to in-review.
gh issue edit <N> --remove-label status:addressing --add-label status:in-review
Report what changed and the PR URL. The owner re-reviews; loop /spec-flow:address again if they
leave more comments, or they squash-merge and you run /spec-flow:finalize <N>.
main — only the issue branch.(description).