sova: Skill for Claude Code

Address PR Review Comments

Score each review comment, address all of them (fix or acknowledge with justification), and reply on GitHub. Handles both human reviewers and automated review bots (Sourcery, CodeRabbit, etc.).

CRITICAL: Complete ALL Steps

This command runs as a headless agent. You MUST execute every step below through to completion. In headless mode, producing a text-only summary without a tool call causes the process to exit immediately, so NEVER output a final summary without having completed steps 9-18 first (capture knowledge, squash, rebase, push, reply, resolve, dismiss). If you discover that all findings are already addressed, you MUST still complete steps 9-12 (capture knowledge, squash, rebase and push) to fold in pending documentation and resolve any merge conflicts, then skip to step 13 to handle thread resolution before the summary.

Incomplete execution is worse than failure: a run that fixes code but never commits/pushes wastes the cost and leaves the PR unchanged.

Instructions

1. Get the PR number from the arguments provided when this skill is invoked.

2. Fetch review data and the PR's branch names:

   gh pr view <PR_NUMBER> --json comments,reviews,body,title,headRefName,baseRefName
   gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/comments
   gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/reviews
   BASE=$(gh pr view <PR_NUMBER> --json baseRefName --jq .baseRefName)
   HEAD_BRANCH=$(gh pr view <PR_NUMBER> --json headRefName --jq .headRefName)
   echo "Base branch: $BASE, head branch: $HEAD_BRANCH"
   

   Every shell block runs in a fresh shell, so variables do not carry over between blocks: each later block that uses BASE or HEAD_BRANCH re-assigns them first with the same two gh pr view lines (or the literal values printed here).

3. Verify this is your PR and that you can push to it (STOP if not, before any worktree or commit work happens). A STOP anywhere in this step must end the run as a failure (a non-zero exit / an incomplete-run outcome), never a clean summary: the supervisor's address-cycle counter only increments on a posted sova-addressed marker (step 15), so a guard STOP that reports cleanly looks like "nothing to do" and the supervisor respawns the sova-address-pr skill on the same PR every poll with no cap on it. Reporting the STOP as a failed run at least makes the repetition visible in the run history; check_repeated_failures_gate() does not apply here (it only gates the researcher and developer roles, never command:address-pr), so today only the already_running concurrency guard prevents a second simultaneous spawn, and nothing caps the respawn count on an unpushable or foreign PR. Closing that gap means wiring command:address-pr into check_repeated_failures_gate(), which is out of scope for this change.