x-fix-epic-pr

Batch-process epic PRs into a consolidated findings report and correction PR.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/edercnj/ia-dev-environment --skill x-fix-epic-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-fix-epic-pr
Source: https://github.com/edercnj/ia-dev-environment/tree/main/src/main/resources/claude/skills/x-fix-epic-pr
Command: npx skills add https://github.com/edercnj/ia-dev-environment --skill x-fix-epic-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Batch-processes epic PRs by discovering all associated PRs, classifying review comments, and producing a consolidated findings report with a single correction PR.

Core Features & Use Cases

  • Discover all PRs from an epic using the execution state data.
  • Classify comments into actionable items, suggestions, questions, and praise.
  • Generate a consolidated findings report and open a single correction PR.
  • Supports dry-run and explicit PR lists with idempotent re-execution.

Quick Start

Provide the epic ID and any flags to batch-process all associated PRs, generate a consolidated findings report, and open a single correction PR.

Frequently Asked Questions about x-fix-epic-pr

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

FAQPage Schema
How do I consolidate review comments from multiple GitHub PRs in an epic into a single fix?

To consolidate GitHub PR reviews, you can batch-process an epic by discovering all associated PRs, classifying review comments into actionable items, and generating a single correction PR with a consolidated findings report.

Can I do a dry run when automating epic PR reviews before applying any code changes?

Yes, dry-run mode is supported for epic PR review automation. It generates a consolidated findings report classifying review comments without applying fixes, allowing you to inspect proposed changes beforehand.

How are review comments classified when batch-processing GitHub PRs?

Review comments are classified into actionable items, suggestions, questions, and praise during batch-processing. This classification helps isolate required corrections from general feedback before generating a consolidated fix.

What's the best way to handle PR review drift when re-running automated epic fixes?

To minimize drift during automated epic PR fixes, the process supports idempotent re-execution and dedupes changes by fingerprint. This ensures re-running the task yields consistent results without duplicating corrections.

Do I need an explicit PR list to batch-process GitHub epic reviews?

You do not need an explicit PR list if you have execution-state.json data. The skill discovers all associated PRs from the epic state data, but you can alternatively provide an explicit list of PRs to target.

Why are duplicate code changes being applied when fixing multiple PRs in a GitHub epic?

Duplicate code changes across multiple GitHub epic PRs are prevented by deduplicating changes through fingerprinting. This mechanism ensures identical corrections are consolidated before opening a single correction PR.