review-fixes

Apply user-selected fixes to unresolved GitHub PR review comments and commit changes.

Updated Oct 17, 2017
One-click install
npx skills add https://github.com/NAKKA-K/dotfiles --skill review-fixes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-fixes
Source: https://github.com/NAKKA-K/dotfiles/tree/main/claude/skills/review-fixes
Command: npx skills add https://github.com/NAKKA-K/dotfiles --skill review-fixes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates identifying unresolved GitHub PR review comments and applying user-selected fixes to code, then commits the changes.

Core Features & Use Cases

  • Identify unresolved pull request review threads (files and line numbers) and extract review content, including prefixes like [must], [imo], or [nits].
  • Present fixes as selectable items (multi-select) with clear prioritization for must-fix issues, and apply edits with minimal changes.
  • Validate and commit changes with a structured message, then report results and guide next steps (e.g., git push).

Quick Start

Provide a PR number to begin; the skill will fetch unresolved reviews, allow you to select fixes, apply them, and commit the changes.

Frequently Asked Questions about review-fixes

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

FAQPage Schema
How do I automatically apply fixes from GitHub PR review comments?

You can automatically apply fixes from GitHub PR review comments by providing a PR number to fetch unresolved threads, interactively selecting which issues to resolve, and committing the minimal code changes with a structured message.

Can I select which unresolved review comments to fix on a pull request?

Yes, unresolved review comments are presented as multi-select items with clear prioritization using must, imo, and nits prefixes, allowing you to interactively choose which fixes to apply to your code.

How does the review-fixes workflow handle commits after applying code fixes?

The review-fixes workflow enforces a read-edit-commit process that validates changes with QA checks, prompts for user approval before pushing, and generates a structured commit message to report results and guide next steps.

Do I need to install any dependencies to automate GitHub PR review fixes?

No additional dependencies are required to automate GitHub PR review fixes, as the skill operates independently to fetch reviews, apply edits with minimal changes, and commit the validated code updates.

What is the best way to manage must-fix and nits comments in a code review?

The best way to manage must-fix and nits comments is extracting review content with prefixes like must, imo, or nits, prioritizing must-fix issues for interactive selection, and applying minimal edits to resolve them.

Why are my unresolved GitHub PR review threads not being picked up for fixes?

Unresolved GitHub PR review threads are fetched by specifying a valid PR number, and the skill identifies files and line numbers from those threads to extract review content and present fixes for interactive selection.