capture-review

Extract and categorize GitHub PR reviewer comments into markdown training test cases.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thomasttvo/claude-skills --skill capture-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-review
Source: https://github.com/thomasttvo/claude-skills/tree/main/skills/capture-review
Command: npx skills add https://github.com/thomasttvo/claude-skills --skill capture-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture noisy or valuable reviewer insights from GitHub pull requests and transform them into consistent, structured training test cases so review agents improve over time and human signals are preserved.

Core Features & Use Cases

  • Selective extraction: Fetch PR metadata and all review comments, then filter to only the target reviewer's top-level comments.
  • Signal vs Context classification: Automatically separate actionable signals (nits, issues, suggestions) from contextual explanations and mark outdated threads with original commit SHAs.
  • Training file generation: Produce or append a markdown test case in a training directory with standardized severity labels and adhoc notes for iterative model training.

Quick Start

Provide a GitHub PR URL and confirm the categorized comment list to save a structured training test case for that PR.

Frequently Asked Questions about capture-review

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

FAQPage Schema
How do I save GitHub PR review comments as training data for code review models?

To save GitHub PR review comments as training data, fetch the pull request metadata and reviewer comments, filter for a specific reviewer's top-level messages, classify them into actionable signals versus context, and write the structured output to a local markdown test case file.

What is the best way to extract actionable signals from noisy pull request review comments?

The best way to extract actionable signals from pull request review comments is to filter out reply threads and acceptance language, categorize the remaining top-level feedback into signals like nits or issues, and mark outdated threads using original commit SHAs.

Can I generate structured test cases from GitHub pull request feedback without modifying the repository?

Yes, you can generate structured test cases from GitHub pull request feedback without modifying the repository because the process only fetches PR metadata and review comments to write or append a local markdown training file without pushing changes back to GitHub.

How do I handle outdated review threads when extracting training data from pull requests?

To handle outdated review threads when extracting training data from pull requests, detect the threads and capture their original commit SHAs so the generated test cases accurately reference the specific code state the reviewer commented on.

Does this PR comment extraction method support appending new feedback to existing markdown training files?

Yes, this PR comment extraction method supports appending new feedback to existing markdown training files by mapping user selections back to comment IDs or ranges and writing or appending the categorized test case into a local training directory.

What limitations exist when categorizing GitHub review comments into severity labels for model training?

A key limitation when categorizing GitHub review comments into severity labels for model training is that the extraction only captures top-level comments from a specific target reviewer, intentionally filtering out reply threads and general acceptance language to focus on distinct signals.