[FEATURE] Resume a self-filed GitHub issue's checklist as the session's task list

Summary

Some GitHub issues are effectively personal working checklists — self-filed by the same person who'll fix them, listing specific sub-items to verify or address (e.g. "9 of 11 gap items need independent verification"). There's no way to turn one of these directly into a Claude Code session with its checklist pre-loaded as tracked tasks. Please add a "resume this issue" flow: paste/reference an issue URL and have its content (especially checklist items) become the session's starting task list.

Current behavior

Opening a Claude Code session against a repo that has a relevant open issue requires manually pasting the issue's content, or the URL, into the chat and asking Claude to read it — there's no direct integration that turns an issue's checklist items into the session's actual tracked todo list. If an issue has an actual - [ ] checklist, that structure is currently discarded in favor of free-text.

Motivation

Self-filed issues used as working checklists are a real, recurring pattern (e.g. QA trackers, data-quality findings written up as issues on a repo, meant to be worked through item by item later). Right now, resuming that work means re-reading the whole issue and manually recreating a task list — the checklist structure that already exists in the issue body gets thrown away and rebuilt by hand every time.

Proposed behavior

1. A command (e.g. /resume-issue <url or number>) that fetches the issue via gh/GitHub API, and seeds the session's task list directly from any - [ ] / - [x] checklist items in the body.
2. Completing a task in the session optionally checks it off in the actual GitHub issue (with confirmation, since this edits public content).
3. Falls back gracefully for issues with no checklist — just loads the issue body as context instead.

Why it matters

• Closes the gap between "I wrote this issue as my own todo list" and "now I'm actually working through it" — currently a manual re-transcription step every time.
• Makes GitHub issues a genuinely two-way integration point (already read from for context in some flows) rather than one-way (filed but not actionable from within a session).

Related issues (adjacent, not duplicates)

• #79087 [FEATURE] Surface stale open PRs that Claude Code opened on the user's behalf — same theme (closing the loop on GitHub items Claude Code touches), different object (PRs vs. self-filed issues) and different mechanism (staleness surfacing vs. resuming as a task list).

Notes

• Reviewed for duplicates before filing (searched "resume GitHub issue as task list session") — nothing found describing this specific ask as of 2026-07-19; existing near-hits were all about background-agent transcript resumption, not GitHub-issue-to-tasklist conversion.
• Should require explicit confirmation before writing back to GitHub (checking off items), per Claude Code's existing stance on side-effectful actions needing user approval.