pr-revise

Categorize GitHub pull request review comments into actionable work items.

11|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/anticorrelator/lore --skill pr-revise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-revise
Source: https://github.com/anticorrelator/lore/tree/main/skills/pr-revise
Command: npx skills add https://github.com/anticorrelator/lore --skill pr-revise

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms raw GitHub Pull Request feedback into organized, actionable work items, ensuring no critical review comments are missed and providing context for efficient resolution.

Core Features & Use Cases

  • Categorizes Feedback: Sorts review comments into clear categories like "Agreed Changes" and "Verification Needed."
  • Knowledge Enrichment: Integrates with your knowledge base to contextualize feedback against project conventions.
  • Automated Work Item Creation: Generates structured work items for tracking and resolution.
  • Use Case: After a complex code review, use this Skill to automatically create a task list that prioritizes critical feedback, flags areas needing further investigation, and notes any conflicts with existing project standards.

Quick Start

Use the pr-revise skill to process feedback on pull request number 123.

Frequently Asked Questions about pr-revise

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

FAQPage Schema
How do I organize GitHub pull request review feedback into actionable tasks?

Organize GitHub pull request review feedback into actionable tasks by fetching comments, categorizing them by actionability, and enriching them with knowledge base insights to generate structured work items with clear directives.

Can I automatically detect pull requests from my current Git branch?

Yes, you can automatically detect pull requests from your current Git branch. The skill supports automated detection of PRs from the current branch and processes multiple reviewer batches sequentially to ensure all feedback is captured.

What is the best way to manage multiple batches of PR review comments?

The best way to manage multiple batches of PR review comments is sequential processing. The skill handles multiple reviewer batches sequentially, fetching comments and categorizing them to ensure no critical review feedback is missed.

Does the skill distinguish between actionable code changes and subjective preferences?

Yes, the skill distinguishes between actionable code changes and subjective preferences. It categorizes feedback into clear groups like Agreed Changes and Verification Needed, separating required modifications from optional stylistic preferences.

How does knowledge base enrichment work for PR feedback?

Knowledge base enrichment contextualizes PR feedback against project conventions. It integrates with your knowledge base to provide context for efficient resolution, flagging areas needing investigation and noting conflicts with existing project standards.

Do I need a knowledge base to categorize pull request feedback?

A knowledge base is not strictly required to categorize pull request feedback, but it is necessary for knowledge enrichment. Without it, the skill can still sort comments into actionable work items based on reviewer intent and actionability.