summarize

/pr:summarize

Given a PR URL or number, fetch all review feedback and produce a clear fix plan.

Step 1: Resolve the PR

Parse the argument for a PR URL (e.g. https://github.com/org/repo/pull/42) or a bare number (e.g. 42 or #42).

• If a full URL is given, extract OWNER, REPO, and PR_NUMBER from it.
• If only a number is given, infer OWNER and REPO from the current git remote:

  gh repo view --json owner,name
  

• If no argument is given, try to find an open PR for the current branch:

  gh pr view --json number,url,headRepositoryOwner,headRepository
  

• If nothing works, ask the user for a PR URL or number.

Step 2: Fetch all review comments

Run both calls with --paginate to avoid missing anything on busy PRs:

# Inline code comments (attached to specific file lines)
gh api repos/OWNER/REPO/pulls/PR_NUMBER/comments --paginate

# Top-level review bodies (overall review text)
gh api repos/OWNER/REPO/pulls/PR_NUMBER/reviews --paginate

Skip reviews where state is APPROVED and the body is empty — those add no signal.

Step 3: Summarize the issues

Group comments by theme or code area (e.g. "workflow permissions", "author login matching", "pagination"). For each group write:

• A short title
• 1–2 sentences describing the concern
• Severity: significant, moderate, or minor

Be concise — this is a map, not a transcript.

Step 4: Categorize by fix type

Split every issue into one of two buckets:

Fixable in the repository — changes to source files, YAML, prompts, configs checked into the repo.

Needs external action — GitHub org/repo settings, secrets, admin permissions, third-party service config. For each, say what needs to happen and who likely needs to do it.

Step 5: Fix plan

List the repository-fixable issues in priority order (significant → moderate → minor). For each:

• What — one line describing the problem
• Where — file and rough location if determinable
• How — a concrete suggestion (specific string to change, flag to add, etc.)

Follow with a short "External actions needed" section listing anything requiring config or admin access, so the user knows what to pursue in parallel.

Keep the whole output skimmable. No padding, no restating the reviewer's comments verbatim.