speckit-resolve-prlisted

# Resolve PR Review Comments ## Capability discovery & grounding Before researching or recommending, enumerate the tools and skills your session actually exposes — do not assume a fixed set; the user may have installed anything — and select the best fit per `${CLAUDE_PLUGIN_ROOT}/skills/speckit-autopilot/references/capability-discovery.md`. Ground every external fact you assert in a real tool, skill, or file result per `${CLAUDE_PLUGIN_ROOT}/skills/speckit-autopilot/references/grounding.md`, and abstain when nothing grounds it. ## Input The user provides either: - A full PR URL: `https://github.com/owner/repo/pull/46` - A full PR review URL: `https://github.com/owner/repo/pull/46#pullrequestreview-123` - Just a PR number: `46` (repo detected from `git remote -v`) ## What to Do ### 1. Parse Input and Detect Repo ```text If full URL provided: Extract OWNER, REPO, PR_NUMBER from URL If just a number: Run `git remote -v`, inspect the actual fetch/push remotes, and select the remote whose normalized GitHub URL identifies the current repository. Never assume that remote is named `origin`; stop on no match or ambiguity. PR_NUMBER = the provided number ``` Check out the PR branch and verify the actual code behavior in that checkout. Never review or remediate from the diff alone. ### 2. Discover Project Commands Read CLAUDE.md and package.json (or equivalent) to find: - BUILD command - TYPECHECK command - LINT command - LINT_FIX command - UNIT_TEST command - INTEG