issuekitlisted

Own the GitHub issue lifecycle in five modes: create issues from a plan or description, start a `ready` issue into its own worktree, close one out once its PR merges, sync PR↔issue links after merge, and triage the tracker for lifecycle, priority, and title gaps. Use when the user says "create issues from this plan", "file an issue", "open a GitHub issue", "log this as a task", "add this to the backlog", "make issues for these TODOs", "start issue #42", "close #42", "sync my issues", "triage the backlog", "set the priority on #42", "relabel #42", "rename issue #42", or "fix the titles on these issues". It runs the tracker only; it writes no plan and no code.
mimukit/skills · ★ 1 · AI & Automation · score 80

Install: claude install-skill mimukit/skills

# issuekit Own the GitHub issue lifecycle through the [`gh` CLI](https://cli.github.com), in five explicit **modes**: - **`create`.** Turn a plan document or a plain description into well-formed issues. - **`start`.** Take a `ready` issue into its own worktree and flip it `in-progress`. - **`close`.** Once its PR has merged, close the issue, unblock what it was holding up, and tear the worktree down. - **`sync`.** Reconcile and repair the PR↔issue relationship *after* the fact (issues a merged PR should have closed, a missing link on an existing PR, a dependent still marked `blocked` by an issue that landed). - **`triage`.** Report the health of the tracker, then offer fixes you approve. One skill, five jobs, because they're the same job at five points in a dev workflow: file the work, pick it up, land it, keep everything in sync as PRs merge, and keep the tracker honest. **`close` vs `sync`.** They do overlapping tracker work and the split is by *scope*, not mechanism: `close` lands **one named issue** whose PR you know merged, and is the only mode that touches the filesystem (the worktree teardown). `sync` sweeps the **whole tracker** for drift after the fact, meaning issues a merged PR should have closed but didn't, missing links, and dependents still marked `blocked` by work that landed, and it never touches a worktree. `close` reuses `sync`'s reconciliation rather than restating it. ## When this fires The user wants to act on GitHub issues. Route to a mode from wha