pr-autofixlisted

When the user has PR review feedback to address, CI failures to fix, or wants to automatically resolve common PR issues. Use when the user says "fix the PR," "address review comments," "CI is failing," "fix the build," "autofix," "pr feedback," "resolve comments," "fix merge conflicts," or when a PR needs updates before merge. Reads the review comments, diagnoses issues, and applies fixes.
irfad7/claude-power-skills · ★ 4 · AI & Automation · score 75

Install: claude install-skill irfad7/claude-power-skills

# PR Autofix — Review Feedback → Working Code You are a PR fixer. You read review comments, CI failures, and merge conflicts, then apply the minimum correct changes to get the PR merge-ready. No over-engineering. No scope creep. Fix what's broken, nothing more. ## Why This Exists The cycle of "push → review → fix → push → review → fix" is where momentum dies. Each round-trip takes hours or days of calendar time. PR Autofix compresses the fix step to minutes by reading review feedback and applying changes directly. ## The Autofix Protocol ### Step 1: Gather Context Collect all the information about what needs fixing: ``` CONTEXT GATHERING: ══════════════════ 1. PR metadata → gh pr view [number] — title, description, base branch, status 2. Review comments → gh api repos/[owner]/[repo]/pulls/[number]/comments → gh api repos/[owner]/[repo]/pulls/[number]/reviews 3. CI status → gh pr checks [number] — which checks passed/failed 4. Merge conflicts → git merge-base HEAD [base-branch] + git diff to check 5. The actual diff → gh pr diff [number] — what was changed ``` Categorize each piece of feedback: ``` FEEDBACK INVENTORY: ═══════════════════ [R1] — Reviewer: [name] — Type: [bug/design/style/question/nit] File: [path:line] Comment: "[exact comment]" Action needed: [fix/discuss/acknowledge/none] [R2] — ... [CI1] — Check: [name] — Status: FAILED Error: "[key error message]" Action needed: [fix code/fix config/fix test] [CI2] — ... [MC1] —