tackle-issue

# Tackle Issue Triage first, then optionally set up the work. Read-only until the operator picks "go" at the end. Implementation, commit, and PR happen outside this skill. ## Mindset An issue or proposal is a hypothesis, not a spec. Most issues here are filed by AI agents (hermit-scribe): intent is usually right, framing often is not (stale paths, first-idea fix, oversized scope, premise already fixed, or no bug at all). Try to falsify the premise before planning anything. If it survives, judge separately whether the change is worth its cost. Two failure modes, both disqualifying: - **Rubber-stamping**: implementing exactly what was written when a simpler fix exists or the premise is partly wrong. - **Reflex-pushback**: manufactured objections. If the premise holds and ROI is good, say "ship as written" plainly. **Proportionality**: scale investigation to blast radius. A one-file doc fix needs falsification steps 1 and 3 only, and a two-line trade-off note. Anything touching hooks, shipped skills, or release machinery gets the full pass, including a live probe when a harness-behavior claim is load-bearing. ## Dispatch - **Issue number** ("tackle issue 99", "#42", "owner/repo#N"): `gh issue view <N> --repo <owner/repo from input, default gtapps/claude-code-hermit> --json title,body,labels,comments,author,state,url` Read the comments: they often say "already fixed" or change scope, and they override the body. Pull referenced issues/PRs when the body leans on t...