fix

Fix: RCA → Fix → Review → Check

Goal: find the root cause, make the smallest fix with a regression test, then Review and Check: the pipeline of /temper, with RCA in place of Intent and Plan, and Fix in place of Build.

First output. Look at your system prompt for a line that starts with Temper enforcement:. With none, your first line is exactly Temper enforcement is off here (no mods support); continuing with prompt based phases. With Temper enforcement: off (UI only), it is exactly Temper enforcement is off (turned off by the user); continuing with prompt based phases. With active, say nothing about it. Say it once per conversation. With the Temper mod, the mod stands aside in a /temper:fix run: it draws nothing for it and judges none of its moves, but nothing goes around the native commit hook. With the mod off, every phase works the same; the mod adds the band, the pane and its write guards. Nothing falls back silently.

Usage

/temper:fix "users get 500 error on checkout"    # start a fix
/temper:fix "JIRA-123"                            # a fix from a ticket
/temper:fix                                       # take up the saved fix

The temper CLI is ${CLAUDE_PLUGIN_ROOT}/scripts/temper. Every path below is written out in full: run it exactly as shown. The commit hook runs temper gate commit on every commit in a project with a .temper folder, so a fix records its evidence like any run: Fix is judged by the build gate (a regression test is a RED then GREEN pair), Review and Check are the same stages as in /temper.

1. RCA (before the run exists)

First run ${CLAUDE_PLUGIN_ROOT}/scripts/temper next --json. When it lists setup, run those calls first, each once, as the Start section of ${CLAUDE_PLUGIN_ROOT}/commands/temper.md says: they install the native commit hook, without which nothing gates the fix's commit.

With no arguments and a fix run active (${CLAUDE_PLUGIN_ROOT}/scripts/temper state get command prints fix), skip to step 2. A /temper run that is active is not this command's: say so in one line and ask its restart question from temper next --json.