跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

address

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.

rustyrazorblade · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add rustyrazorblade/skills --skill address

技能说明


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]

address — resolve the owner's PR review comments

You are this issue's issue-manager, running as your own dedicated background 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). You're already running inside this issue's worktree — Claude Code's own background-session isolation put you there, on whatever branch it assigned; resolve it with git rev-parse --abbrev-ref HEAD rather than assuming a name. If you need to recover the PR from scratch (not already known from context), search by issue instead of by branch name: gh pr list --search "Closes #<N> in:body" --json number,headRefName.

Steps

  1. Check the repo's configuration first, before any work. Run:

    bash ${CLAUDE_PLUGIN_ROOT}/scripts/repo-config.sh check
    

    Non-zero: stop here, having done nothing, and relay the script's output verbatim. Add no rules, no explanation, and no fallback of your own. Do not offer to create the file; that offer is project-manager's alone.

    Find the PR and fetch review comments.

    BR=$(git rev-parse --abbrev-ref HEAD)
    gh pr list --head "$BR" --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.

  2. Mark addressing.

    gh issue edit <N> --remove-label status:in-review --add-label status:addressing
    
  3. 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:

    • behavior/test/structure changes → tdd-developer (test-first);
    • review-rule/spec-conformance concerns → reviewer to re-check after fixes, or build-engineer for build/lint/format. Instruct it to make focused commits and to never push or touch main. For its test gate, append this verbatim to its prompt — the same generated line implement uses, never a second copy of it, and never a tier, command, or policy restated here:
    bash ${CLAUDE_PLUGIN_ROOT}/scripts/repo-config.sh instruction
    

    Step 1's check has already confirmed the policy is there, so add no missing-file clause. If any comment references a CI failure rather than a human review note, run /spec-flow:sync-ci <N>'s own mechanics first (its SKILL.md steps 3-5) so the failing test lands in .spec-flow/flagged-tests before the fix agent starts — otherwise its local gate has nothing to catch the actual failure against, and it ends up fixing blind and pushing on a guess.

  4. Push the branch (outward-facing — done here, narrated). Re-resolve $BR fresh — cheap, and this may be a separate Bash call from step 1's, which wouldn't have carried it over:

    BR=$(git rev-parse --abbrev-ref HEAD)
    git -C <worktree> push origin "$BR"
    

    Single check, not a wait: check once whether the CI run tied to this new push is red — whether or not step 3 already synced a failure in, since the fix round itself is a likely source of a fresh regression — gh run list --branch "$BR" --json databaseId,status,conclusion,headSha --limit 10 --jq '.[] | select(.headSha == "'"$(git -C <worktree> rev-parse HEAD)"'")'. status not yet completed → move on, nothing more to do here. conclusion is failure → run /spec-flow:sync-ci's own mechanics right here (its SKILL.md steps 3-5: download the spec-flow-failures artifact, append the ids to .spec-flow/flagged-tests), the same way step 3 above and implement step 5 both do it — not the whole skill. A regression this round introduced is otherwise never recorded, and the next run has no memory of it. Then don't loop silently; report it plainly in step 6 as still broken (or flaky) rather than declaring the round done.

  5. Reply per thread. For each review comment you addressed, post a reply noting the commit that resolved it. Reply to the thread's root comment id, not to a reply within it — the replies endpoint only accepts a top-level review comment id and 422s on a reply-to-a-reply:

    gh api repos/{owner}/{repo}/pulls/<PR>/comments/<root-comment-id>/replies \
      -f body="Addressed in <short-sha>: <one line>."
    
  6. Back to in-review.

    gh issue edit <N> --remove-label status:addressing --add-label status:in-review
    gh issue comment <N> --body "🔧 Addressed <N-comments> review comment(s), pushed \`<short-sha>\`."
    

    Report what changed and the PR URL. State what changed and what is still broken in plain terms; if you name a review thread, a comment, or a test, say what it is, and let any identifier ride as a trailing tag only — the Presenting to the owner contract in docs/workflow.md. 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>.

Rules

  • Never merge, never push to main — only the issue branch.
  • Tolerate the zero-new-comments case gracefully.
  • Reply to the actual review threads so the owner sees resolution in context, not just a force-push.
  • When you cite an issue or PR, always write it as <number>: <title>, on its own line with a
阅读完整来源 ↗