Resolve Blocking PR Review Findings

VerifiedSafe

Resolves blocking review findings on an existing pull request with minimal changes, without broadening scope, including focused regression tests.

Sby Skills Guide Bot
DevelopmentIntermediate
9/14/2026
Claude Code
#code-review#pull-requests#git-workflow#regression-testing#scope-control

Recommended for

Automated summary

Resolves blocking review findings on an existing pull request while keeping the change strictly within the PR's current scope, with focused regression tests and a per-finding status report.

Strengths

  • Requires each blocking finding to be independently verified before any code is changed
  • Explicitly caps changes at the minimum needed and skips unrelated non-blocking suggestions
  • Mandates focused regression tests when behavior changes, then a re-review of the touched area and its regression boundary
  • Ends with a clear per-finding report: resolved, not reproduced, or still unresolved

Limitations

  • Depends heavily on AGENTS.md and on a PR number passed as an argument; without them the workflow is incomplete
  • Not intended for non-blocking suggestions or for deliberately widening the scope of the PR
  • Assumes a git repository with push access, since the final step commits and pushes without merging
When to use it

Use it when an open PR is blocked by review comments that need to be cleared without reopening design discussions.

When not to use it

Avoid it when the review calls for a design overhaul or a scope change, or when the PR has no identified blocking findings yet.

Security analysis

Safe
Quality score85/100

The skill instructs a coding agent to review an existing PR, make minimal code changes, run tests, and commit/push fixes. It does not contain destructive commands, exfiltration, obfuscation, or disabling of safety controls. Git commit and push are standard, legitimate development actions with no meaningful security risk.

No concerns found

How this analysis is made

Examples

Fix blocking review comments
/address-review 412 — resolve the unresolved blocking comments on this PR and report the status of each one.
Re-run after re-review
Use the address-review skill on PR 87: verify each blocking finding, apply only the minimal fix, add regression tests, then commit and push without merging.

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.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/resolve-blocking-pr-review-findings-mu0qzo55/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/resolve-blocking-pr-review-findings-mu0qzo55' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/resolve-blocking-pr-review-findings-mu0qzo55/download' --output '.skill-downloads/resolve-blocking-pr-review-findings-mu0qzo55/SKILL.md.part' && mv '.skill-downloads/resolve-blocking-pr-review-findings-mu0qzo55/SKILL.md.part' '.skill-downloads/resolve-blocking-pr-review-findings-mu0qzo55/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/resolve-blocking-pr-review-findings-mu0qzo55/SKILL.md' && test -s '.skill-downloads/resolve-blocking-pr-review-findings-mu0qzo55/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/address-review' && cp -R '.skill-downloads/resolve-blocking-pr-review-findings-mu0qzo55' '.claude/skills/address-review'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/resolve-blocking-pr-review-findings-mu0qzo55'

openskills read 'resolve-blocking-pr-review-findings-mu0qzo55'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/resolve-blocking-pr-review-findings-mu0qzo55/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills