kicad-tools: Command for Claude Code

/repo:reset — Back to Baseline

The end-of-task ritual: review and prune stale git state, sync with the remote, and land back on the default branch with a clean working tree. The reversible steps (fetch, land on the default branch) run by default; nothing irreversible — dropping a stash, deleting a branch or worktree — ever happens without an explicit opt-in and the permanent-loss check.

Usage

/repo:reset                    # Run the reversible baseline steps; keep all stashes, land on default
/repo:reset --ask              # Confirm each step before acting
/repo:reset --prune            # Also delete confirmed-safe branches/worktrees (after the loss check)

Two halves

The steps below split cleanly in two, and naming the split matters because callers can schedule the halves separately:

• Sync-and-switch (reversible — steps 1 and 4): the working-tree safety check, git fetch --all --prune, and landing on an up-to-date default branch. Nothing is removed.
• Pruning (gated — steps 2 and 3): stash review and branch/worktree review. These can permanently remove work, so they keep the explicit opt-in and the [[branches]] permanent-loss check.

Run standalone, /repo:reset always runs all four steps in order, exactly as documented — this split changes nothing here. It exists because [[all]] may run the sync-and-switch half early (before its Docs stage) when the current branch is fully pushed and behind the default branch, so that its doc stages don't edit a stale checkout; the pruning half still runs last there, with its gates intact.

Steps

1. Working tree safety check

Refresh the remote-tracking refs before looking at the tree, so the one judgment call this command asks for is made against the current remote rather than a picture up to three steps stale:

git fetch --all --prune
git status --porcelain

The fetch is read-only: it updates remote-tracking refs and drops the ones that no longer exist on the remote. It moves no local branch, touches no index, and rewrites no working-tree file, so it is safe ahead of the safety check and changes none of this command's ordering guarantees. --prune now runs once, here, instead of at step 4 — which also means the branch & worktree review in step 3 sees already-pruned remote-tracking refs rather than pruning them afterwards.