resolve-review

Name: resolve-review
Availability: InStock
Author: refined-prun

Apply review resolutions from PR review files with per-finding commits.

35|27|Updated Jul 6, 2024

Search Tags:#git #workflow #code review #pull request #commit #repository #branch validation

Ready to run

npx skills add https://github.com/refined-prun/refined-prun --skill resolve-review-refined-prun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resolve-review
Source: https://github.com/refined-prun/refined-prun/tree/main/.claude/skills/resolve-review
Command: npx skills add https://github.com/refined-prun/refined-prun --skill resolve-review-refined-prun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns written PR review resolutions into concrete code changes, so you can clear feedback without manually tracking each finding.

Core Features & Use Cases

Per-finding resolution: Applies fixes or dismissals from .tmp/pr/<number>/pr-review.md one finding at a time.
Safe PR workflow: Verifies the target PR, checks branch alignment, and skips unresolved items until the user adds instructions.
Commit discipline: Creates a separate commit for each applied fix and updates the review file to remove resolved findings.
Use Case: After a review flags several issues, use this Skill to implement the agreed changes, record them cleanly in git, and keep the review document in sync.

Quick Start

Ask the assistant to resolve the review findings for the current PR, and it will apply your written resolution notes, commit each fix separately, and update the review file.

Frequently Asked Questions about resolve-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I apply code review fixes from a pull request one commit at a time?▼

Apply code review fixes by reading resolution notes from `.tmp/pr/<number>/pr-review.md`, validating the git branch, editing files, and creating an isolated commit for each resolved finding. The review file updates automatically to remove resolved items.

How does resolving PR review findings work with my existing git workflow?▼

Resolving PR review findings checks git status, validates branch alignment with the target PR, applies written resolutions to critical, suggestion, and observation findings, and commits each fix separately to maintain a clean git history.

What do I need to start resolving pull request review findings?▼

You need an existing review file stored at `.tmp/pr/<number>/pr-review.md` containing your written resolution notes. The Skill skips unresolved items until you add instructions, ensuring all applied fixes have explicit guidance.

Can I resolve specific PR review findings or do I have to process all of them at once?▼

You can resolve specific PR review findings by adding your resolution notes to the review file. The Skill processes each finding individually, skipping any unresolved items until you provide instructions for them.

What happens to the review file after I apply a fix to a pull request finding?▼

After applying a fix, the review file is updated to remove the resolved finding. This keeps your review document in sync with the actual code changes and prevents duplicate work on already resolved items.

Why are my PR review findings being skipped during resolution?▼

PR review findings are skipped when the review file lacks written resolution notes for those specific items. The Skill requires explicit user instructions for each finding before it edits files and commits the fix.