dancing-bear: Skill for Claude Code

Review, Fix, and Resolve PR Threads

Delegates to workflows/code/review-fix-threads.yaml. Runs unattended from "here is a PR" to "every thread has a reply and is resolved".

When to Use

• A PR has Copilot and/or human review threads waiting on the author
• The user says "address the feedback", "fix the review comments", "resolve the threads"
• Feedback has already been reviewed and now needs remediation

Use /code-review instead when the PR needs reviewing — this skill consumes review threads that already exist, it does not produce them.

Autonomy

There is no human gate. The workflow posts replies and resolves threads without confirmation, including on threads it decided not to action — a rejected or moot thread gets a reply explaining why, then is resolved.

What constrains it:

• verify-fixes reports itself failed and exits non-zero when tests, lint, or coverage are not green, which halts the run before anything is posted.
• resolve-threads re-checks all_green itself and fails closed: a missing, unparseable, or ambiguous verification file aborts the stage. It reads the path from resolve-plan.json's verify_file rather than guessing, since the two callers of that fragment keep the file in different places and a hardcoded path would silently find nothing for one of them.
• plan-resolution will not compose replacement prose at the moment of posting: a missing replies file produces an empty plan and a non-zero exit.
• A reply always posts before its thread resolves. A resolve whose reply failed is skipped and reported.
• Threads whose fixer crashed, or whose fix was never tested, are never resolved and never receive a reply claiming a fix.
• context and defer threads are never resolved — including threads deferred by the max_threads ceiling, since that is a scheduling outcome rather than a judgement about the comment.
• Every rejection is recorded with evidence in the final report, so the calls made on your behalf can be audited after the fact.