augment-review

Extract human review comments from a working copy into a pull request review file.

35|27|Updated Jul 6, 2024
One-click install
npx skills add https://github.com/refined-prun/refined-prun --skill augment-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: augment-review
Source: https://github.com/refined-prun/refined-prun/tree/main/.claude/skills/augment-review
Command: npx skills add https://github.com/refined-prun/refined-prun --skill augment-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures human review comments added directly in source files and converts them into structured pull request findings, so teams can preserve feedback without manually rewriting it.

Core Features & Use Cases

  • Comment Extraction: Reads the working copy diff and turns added comments into review findings.
  • Safety Validation: Refuses to run if the diff contains code changes instead of comment-only additions.
  • Review File Management: Appends new findings to an existing PR review file and keeps numbering consistent.
  • Use Case: A reviewer annotates files with inline notes, runs the Skill, and gets those notes preserved in a formal review summary that can be resolved later.

Quick Start

Use augment-review to capture the comments in the working copy, append them to the PR review file, and reset the branch.

Frequently Asked Questions about augment-review

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

FAQPage Schema
How do I turn inline code review comments into structured pull request findings?

To turn inline code review comments into pull request findings, extract human annotations from your working copy diff and append them as structured findings to a PR review file. This preserves reviewer feedback without manual rewriting.

How do I extract comments from a git diff and append them to a PR review file?

Extract comments from a git diff by parsing the working copy changes, detecting comment syntax, tracking line numbers, and appending deduplicated findings to an existing PR review file while maintaining consistent numbering.

Can I use this code review workflow if my diff contains actual code changes?

No, this code review workflow refuses to run if the diff contains code changes instead of comment-only additions. Safety validation ensures only comment annotations are processed before resetting the working tree.

What is the best way to preserve review feedback before resetting a git working tree?

The best way to preserve review feedback before resetting a git working tree is to capture inline source file annotations, validate comment-only changes, and append them to a formal PR review summary for later resolution.

Does this PR review tool deduplicate findings against existing review comments?

Yes, this PR review tool deduplicates findings against existing review comments. It parses diffs, detects comment syntax, tracks line numbers, and ensures new findings are appended without duplicating existing entries in the review file.

Why does the working copy reset matter when extracting pull request findings?

The working copy reset matters because it safely cleans up annotated source files after extracting pull request findings. This preserves the formal review summary while returning the branch to its original state for subsequent development.