agent-glovebox: Skill for Claude Code

Writing the end-of-session handoff

The doctrine

Fix what is yours, route what is shared, hand off the remainder. Root CLAUDE.md § Autonomy's scope rule decides which of the three a failure is. A handoff entry is one its arm 3 leaves: not caused by your change, and not blocking your outcome. A failure your own diff caused is yours. A shared one goes to its owner, is named here in one line with that owner, and is never re-fixed here. A clean session writes nothing and says nothing — never "no handoff needed".

An intermittent test failure is not a handoff item. The ci-triage skill owns it, including the rule that hardware you lack is never an exit. Two flakes still hand back, one line each: one an OPEN PR already covers (name that PR), and one blocked by a credential you lack that stops you from committing a runnable reproduction at all (name the credential).

The four steps

1. Fix what the scope rule's arm 1 makes yours. Work every such item on this branch until only the unreachable remain. Needing another PR is not a reason to defer — open it. A request for a handoff asks for the residue. It is never leave to stop early. A review finding on a PR this session opened is arm 1, and so is a question only a live run answers: CI has KVM, so dispatch that run. An item you still leave gets one line saying what blocks it.
2. Earn "pre-existing". Reproduce the failure on the unmodified base before you call it unrelated:

   umask 002 && git worktree add --detach /tmp/claude-worktrees/base origin/main
   

   Then run the exact failing command there and quote what it printed. A claim you did not run is a hypothesis, and it says so. Reproducing it on the base earns "pre-existing", which makes it a SHARED failure rather than "not mine": step 3 finds its one owner, and you reuse that owner's change instead of writing a second one. With no owner, follow ci-triage's ownership rule and take the repair. Merge origin/main into your branch and run it again before you hand anything back — a failure only that merge produces is yours however green both sides are alone.
3. Deduplicate. Search issues and pull requests, because a multi-PR effort is tracked by an issue that no PR search finds:
   • mcp__github__search_issues and mcp__github__search_pull_requests, both with owner/repo and fields: ["number","state","title"].
   • gh pr list --search is GraphQL and answers 403 in a web session, so the MCP tools are the only route that works on both surfaces.
   • An OPEN tracking issue owns the item: add your row by EDITING that issue, and file no second one.
   • Read the PR state: OPEN gets one line naming it and no fresh investigation; MERGED means main already carries the fix, so drop the item; CLOSED covers nothing, so the item stands.
4. Paste it in chat, in full. Never a bare file path: on the host the reader has no shell to open one, and inside the sandbox /tmp dies at teardown. Commit a copy only when it is worth keeping.