pr-review-ingest

Classify GitHub PR review comments and propose rule additions for uncovered findings.

3|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill pr-review-ingest-arangogutierrez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review-ingest
Source: https://github.com/ArangoGutierrez/claude-toolkit/tree/main/.claude/skills/pr-review-ingest
Command: npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill pr-review-ingest-arangogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? PR review feedback often disappears after a merge, so the same bug, architecture, or security issues resurface in later reviews. This Skill fetches a pull request's review comments, classifies each one by category, and checks whether your rules/ directory already covers the substantive findings, proposing a new rule only where a gap exists. ## Core Features & Use Cases - Comment classification: Fetches top-level comments and inline review threads via the gh CLI and sorts each into style, bug, architecture, security, testing, or nit categories. - Rule gap analysis: For bug, architecture, and security comments, checks rules/ for existing coverage and proposes an addition only when none exists. - Recurrence discipline: Treats a single comment as a note rather than a pattern — security findings are proposed immediately, while bug and architecture findings wait for a second occurrence. - Use Case: After a tough review on PR #482, run the Skill to get a per-category tally of feedback and a draft rule proposal for the security comment that had no matching rule. ## Quick Start Ask the assistant to run /pr-review-ingest on PR 482 to classify its review comments and propose any missing rules.

Frequently Asked Questions about pr-review-ingest

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

FAQPage Schema
How do I turn GitHub PR review comments into coding rules?▼

Run the Skill with a PR number or URL, and it fetches the review comments via the gh CLI, classifies each by category, and proposes a rule addition for bug, architecture, or security findings that lack existing coverage in your rules directory.

How to fetch inline PR review comments with the gh CLI?▼

The included script calls gh pr view for top-level comments and gh api repos/{owner}/{repo}/pulls/{number}/comments for inline review threads, formatting each with file path, line, author, and body.

Does this detect recurring issues across multiple PRs?▼

No, each invocation is stateless and sees only one PR. A single comment is noted rather than promoted; pair it with a reflection or mistake-capture workflow to track recurrence before a rule is written.

When are security comments promoted to rules?▼

Security comments are always proposed as rule additions on first occurrence, while bug and architecture comments wait for a second occurrence. Nothing is written to the rules directory without your approval.

What are the requirements to run the PR review parsing script?▼

You need the GitHub gh CLI installed and authenticated with access to the target repository, and the script must run from within that repo so gh can resolve the owner and repo for API calls.