Resolve blocking PR review findings

VerifiedCaution

Fixes only blocking review findings on an existing pull request with focused regression tests, without expanding scope.

Sby Skills Guide Bot
DevelopmentIntermediate
1010/18/2026
Claude Code
#code-review#pull-requests#git-workflow#regression-testing#minimal-diff

Recommended for

Our review

Resolves blocking review findings on an existing pull request with minimal, scope-preserving fixes.

Strengths

  • Independently verifies each blocking finding before touching code, so false positives get filtered out.
  • Enforces the smallest possible change and explicitly skips unrelated non-blocking suggestions.
  • Adds or updates focused regression tests whenever the fix changes behavior.
  • Ends with a report that classifies every original finding as resolved, not reproduced, or still unresolved.

Limitations

  • Assumes AGENTS.md, the PR, its issue, and the review comments are reachable through the repo's tooling; no fallback is described.
  • Stops at commit and push — merging is left as a separate manual step.
  • Gives no guidance for escalating a genuine disagreement with a reviewer beyond marking the finding not reproduced.
When to use it

Use it when an open PR is blocked by unresolved review comments and you want a targeted fix rather than a broader rework.

When not to use it

Avoid it for redesigning architecture, implementing new features, or working through non-blocking review suggestions.

Security analysis

Caution
Quality score80/100

The skill uses powerful actions such as git commit/push and running project-defined tests. These are legitimate for addressing review feedback, but they modify remote state and execute repository code, so caution is warranted.

Findings
  • •Instructs committing and pushing code changes without explicit human approval, which could propagate incorrect or harmful edits to the shared repository.
  • •Instructs running tests and deterministic checks from AGENTS.md, which may execute arbitrary project scripts.

Examples

Fix blocking findings on a numbered PR
/address-review 482
Fix blockers only, skip suggestions
Address the unresolved blocking review comments on PR #312, make the minimal fixes with regression tests, and don't take on the non-blocking suggestions.
Verify before fixing
Go through the unresolved review comments on the current PR, tell me which ones don't reproduce, and only fix the ones that are valid blocking issues.

name: address-review description: Resolve blocking review findings on an existing PR without broadening its scope. argument-hint: "[pr-number]" disable-model-invocation: true

Address unresolved review findings for PR $0.

  1. Read AGENTS.md, the PR, its Issue, current diff, and review comments.
  2. Identify unresolved blocking findings and verify each one independently.
  3. Make the minimum change required to resolve valid blocking findings.
  4. Do not implement unrelated non-blocking suggestions.
  5. Add or update focused regression tests where the fix changes behavior.
  6. Run focused tests and deterministic checks required by AGENTS.md.
  7. Re-review the changed area and its direct regression boundary.
  8. Commit and push the fix. Do not merge.

Report each original blocking finding as resolved, not reproduced, or still unresolved.

Related skills