菜单
Use after a PR merges, or on request, to capture human review comments from a PR into the harness feedback store ("capture the review comments", "harvest PR feedback"). Routed from the merge step.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | harness-capture-review |
| description | Use after a PR merges, or on request, to capture human review comments from a PR into the harness feedback store ("capture the review comments", "harvest PR feedback"). Routed from the merge step. |
Capture human PR review comments into the feedback store as
review-comment events, so harness-report can later turn recurring
review feedback into new guardrails. Bots are skipped; capture is
idempotent (deduped on the GitHub comment id) and never blocks the merge
that preceded it.
Determine the PR. Use the explicit PR number if given, else the PR for the current branch:
gh pr view --json number,url,author
Resolve owner/repo with gh repo view --json nameWithOwner.
Fetch human review data (two sources):
gh api "repos/<owner>/<repo>/pulls/<pr>/comments" --paginate
gh api "repos/<owner>/<repo>/pulls/<pr>/reviews" --paginate
The first is inline comments (fields id, user.login, user.type,
path, line, body, diff_hunk, html_url). The second is review
summaries (use entries with a non-empty body; user, state,
html_url).
Normalize both into one array where each element has: commentId
(the numeric id), authorType (user.type), author (user.login),
isPrAuthor (true when user.login equals the PR author), body,
file (path or null for summaries), line (or null), diffHunk
(diff_hunk or null), commentUrl (html_url). Write it to a temp
JSON file.
Capture:
& "${CLAUDE_PLUGIN_ROOT}/scripts/capture-review.ps1" -InputJson <temp> -Pr <pr> -PrUrl <url>
Report the one-line summary the script prints. If any gh call
fails (no PR, no auth, offline), say so and stop — do not retry in a
loop and do not treat it as fatal to the surrounding work.
Use when creating a new .NET CLI/console project from the agent-harness template ("new cli tool", "new console app", "new dotnet project"). Scaffolds, stamps provenance, and verifies guardrails.
Use when creating a new .NET ETL/API service from the agent-harness template ("new api", "new etl service", "new backend service"). Scaffolds, stamps provenance, and verifies guardrails.
Use when creating a new Expo/React Native app from the agent-harness template ("new expo app", "new mobile app", "scaffold an app with payments"). Scaffolds, stamps provenance, and verifies guardrails.
Use at session start when config-doctor reports the project is not build/deploy-ready, or when the user asks to set up the project - interviews the user, gets EAS logged in / project linked / iOS credentials provisioned and a real bundle id, offers optional payments/auth/API config, and records decisions so the session-start nudge goes quiet
Use when asked to report harness feedback, promote captured guardrail failures into issues, or check "anything worth turning into a rule?". Clusters unreported feedback events and raises digest issues on the agent-harness repo.
Use when asked to update the harness, pull the latest template/guardrail changes, or sync a project with the agent-harness repo. Works in any project previously scaffolded from an agent-harness template.