/fix-pr

name: fix-pr
description: Address PR/MR review feedback by reading comments, implementing fixes, and resolving threads. GitHub and GitLab support.
usage: /fix-pr [<pr-number> | <pr-url> | <mr-url>] [--dry-run] [--from <step>] [--to <step>] [--commit-strategy single|separate|manual] [--no-insights] [--skip-validate] [--stack] [--no-stack] [--base <branch>]
extends: "superpowers:receiving-code-review"

Enhanced PR/MR Fix

A progressive workflow for addressing PR/MR review feedback, following the attune pattern. Supports both GitHub PRs and GitLab MRs via `leyline:git-platform` detection. **analyze** → **triage** → **plan** → **fix** → **validate** → **complete**

When To Use

Use this command when you need to:

• Responding to PR/MR review comments systematically
• Iterating on PR/MR after reviewer feedback

When NOT To Use

• Simple changes that don't need the full workflow
• Work already completed through another sanctum command

Quick Reference

/fix-pr                        # Full workflow
/fix-pr --from triage          # Skip analysis, start at triage
/fix-pr --to plan              # Stop after planning (dry run)
/fix-pr --scope minor          # Auto-skip steps for minor fixes
/fix-pr --stack                # Fix every PR in the stack in one run
/fix-pr --stack --base main    # Override the stack base branch
/fix-pr --no-stack             # Force single-PR mode

Workflow Steps Overview

| Step | Purpose | Skip When | |------|---------|-----------| | **1. Analyze** | Fetch PR, comments, context | Already familiar with PR | | **2. Triage** | Classify comments by type/priority | Single simple fix | | **3. Plan** | Generate fix strategies | Fixes are obvious | | **4. Fix** | Apply code changes | Just need validation | | **5. Validate** | Run tests, version checks, agent-verify manual test plan, then `validate-pr` diff-derived plan with revert-test quality check | Already validated | | **6. Complete** | **Reconcile all unworked items**, **reply to & resolve threads** (required), create issues, post summary | Never - issue tracking & thread resolution enforced |

**Detailed Steps**: See [Workflow Steps](fix-pr-modules/workflow-steps.md)

Intelligent Step-Skipping

The workflow auto-detects scope and suggests step-skipping:

**Minor scope** (1-2 simple comments):

• Skip: Analyze, Triage, Plan
• Run: Fix → Validate → Complete

**Medium scope** (3-5 comments, clear fixes):

• Skip: Analyze (if familiar)
• Run: Triage → Plan → Fix → Validate → Complete

**Major scope** (6+ comments, complex changes):

• Run all steps

# Detect scope automatically
/fix-pr --scope auto

# Override with explicit scope
/fix-pr --scope minor
/fix-pr --scope medium
/fix-pr --scope major

Documentation

| Document | Purpose | |----------|---------| | **[Workflow Steps](fix-pr-modules/workflow-steps.md)** | Detailed guide for each step (Analyze → Complete) | | **[Configuration & Options](fix-pr-modules/configuration-options.md)** | Command options, configuration, best practices | | **[Troubleshooting](fix-pr-modules/troubleshooting-fixes.md)** | Error handling, known issues, migration notes |

Common Usage Examples

Basic Usage

# Full workflow for PR
/fix-pr 123

# With PR URL
/fix-pr https://github.com/org/repo/pull/123

Step Control

# Skip to specific step
/fix-pr --from plan

# Stop at specific step (dry run)
/fix-pr --to plan

# Run specific range
/fix-pr --from triage --to validate

Commit Strategies

# Single commit for all fixes (default)
/fix-pr --commit-strategy single

# Separate commit per fix
/fix-pr --commit-strategy separate

# Manual commits (for complex cases)
/fix-pr --commit-strategy manual

Scope Control

# Auto-detect scope
/fix-pr --scope auto

# Force minor workflow (skip to fix)
/fix-pr --scope minor

Stack Mode (Multi-PR Fix)

When the target PR is part of a stack of dependent PRs rooted at a common base branch, `/fix-pr` can apply the fix workflow to every PR in the stack in one invocation. Each PR still passes its own Gate 1 (thread resolution) and Gate 2 (issue tracking); the root PR additionally receives a consolidated stack-level summary.

# Explicit: fix every PR in the stack containing PR 123
/fix-pr 123 --stack

# Override the base branch (default: master)
/fix-pr 123 --stack --base main

# Force single-PR mode even if a stack is detected
/fix-pr 123 --no-stack

**Behavior**:

1. Before Step 1 (Analyze), `/fix-pr` loads `Skill(sanctum:stack-mode)` to resolve stack membership. Detection uses three strategies: branch naming (`stack/<feat>/<slice>`), the `## Stack` summary comment posted by `stack-push`, and a base-chain walk via `gh pr view --json baseRefName`. 2. Without `--stack` but with a detected stack of size >= 2, the command prompts before iterating. Default is single-PR mode. 3. With `--stack`, Steps 1-6 run once per PR in base-to-tip order. Scope detection is per-PR, so one stack can mix minor and major scopes across its members. 4. Both mandatory exit gates (thread resolution and issue tracking) run per-PR, unchanged. 5. After successful iteration, a single stack summary comment lands on the root PR listing each PR, its fix status, and a link to its per-PR Gate 2 reconciliation comment. 6. If any PR fails its gates, iteration halts. Downstream PRs are left untouched because their review context may now be stale.

**Commit strategy interaction**: with `--commit-strategy single` (the default), each PR gets one commit. With `--commit-strategy separate`, each fix within a PR gets its own commit. Neither crosses PR boundaries: per-PR branch isolation is preserved.

**Stack-mode contract**: see `Skill(sanctum:stack-mode)` for the shared detection, iteration, and summary format used by both `/fix-pr --stack` and `/pr-review --stack`.

Quick Start

1. **Simple PR fixes** (1-2 comments):

   /fix-pr