gopherstack: Skill for Claude Code

gopherstack session close

Work is not complete until git push succeeds and git status shows up to date with origin. Committed-but-unpushed work is stranded and the exact failure this protocol exists to prevent. Never end a session on "ready to push when you are" — push it yourself.

Pre-flight checklist

1. Anything left to do? File a bd issue for it — don't leave it in your head or a comment.
2. Did code change? Run the gate subset for what changed (see gopherstack-gates skill for the decision table; short version below).
3. Any bd issues you worked finished, or in progress? Update their status.
4. Run the push sequence below, in order, without skipping steps.
5. Confirm git status literally says up to date with origin before reporting done.

Ordered close sequence

# 1. File issues for anything unfinished (repeat per item)
bd create --title="<title>" --description="<desc>" --type=task --priority=<0-4>

# 2. Gates, only if code changed — see gate-subset table below

# 3. Update tracker state
bd update <id> --claim        # if you're taking something on
bd close <id> [--reason="<why>"]

# 4. Audit trailers on the branch, before the PR is squashed; reconcile any
#    TRAILER MISMATCH / TYPO'D TRAILER ID findings
task bd-audit

# 5. MANDATORY push sequence — do not stop partway
# Do NOT run `bd dolt push`: embedded Dolt, no remote, silently does nothing
git pull --rebase
git add .beads/issues.jsonl   # bd's auto-export hook usually does this
git push
git status                    # MUST show "up to date with origin"

If git push fails, resolve and retry until it succeeds. Do not leave the session with unpushed commits, even if the failure looks like someone else's problem (rebase conflict, stale branch, etc.) — resolve it.

Gate subset by what changed