Snap Resolve

Triage, fix, explain, close loop.

Workflow

1. Fetch: Gather PR title, PR body, PR comments, review threads, review bodies, unresolved thread ids, CI failures. Extract linked refs/URLs from PR body + comments/reviews. For each resolvable issue ref, fetch title/body/comments. Read parent PRD/epic, breakdown comments, plan comments, and referenced issues/PRs/discussions/docs that affect fix scope. Recurse through material scope/acceptance/blocker links. Support #123, owner/repo#123, full GitHub issue URLs, and closing-keyword forms like closes, fixes, resolves. Normalize + dedupe refs by canonical identity. Route unreadable, invalid, or conflicting refs to Unsure.
2. Explore: Read fetched PR/issue context first, then affected code, tests, patterns before touching fixes.
3. Categorize: Split into [FIX] and [EXPLAIN]. Scope decisions against PR intent + linked issue context. Use TDD for substantive fixes. Use direct fixes for trivia.

Lifecycle

Present one checkpoint summary:

• [FIX]
• [EXPLAIN]
• CI failures
• Unsure

Checkpoint shape: