Playbook on Tokenise

Your overnight Claude Code run died at 2am. A StopFailure hook and a 30-line wrapper decide whether to wait or wake you

Thu, 29 Oct 2026 07:13:00 +0000

A nightly job asks Claude Code to migrate forty files. At 2:14am the API returns a server error, the run ends mid-migration, and the cron job exits non-zero into a log nobody reads. At 8am the working tree is half changed, the log says API Error, and the only way to find out whether that was a thirty-second blip or an expired key is to read it and guess.

A Claude Code status line that tells you when the diff is too big to review

Wed, 21 Oct 2026 07:06:00 +0000

Somewhere around the third hour of a good agent session, the diff stops being something you can review. It started as a three-file change. Now it’s forty files, one of them renamed twice, and the pull request you were going to open at lunch needs an afternoon of reading before anyone else sees it. Nothing went wrong at any single step. Nobody was watching the number.

Pin a legacy function before an agent refactors it: record its outputs, then let StrykerJS grade the safety net

Tue, 20 Oct 2026 07:07:00 +0000

A function nobody wants to touch decides what customers pay, and an agent has just been asked to tidy it. The tests are thin, the original author left in 2021, and the diff that comes back reads fine. That’s the trap. A refactor that reads fine and changes a rounding rule is the most expensive kind, because nothing fails until an invoice does.

Lint your Claude Code subagent files before commit, because a typo makes them quietly do nothing

Sat, 17 Oct 2026 07:04:00 +0000

A teammate adds a reviewer subagent to the repo. It reads well, the pull request gets approved, and from then on nobody notices that the agent never has the tool restrictions they wrote, or never loads at all. One field was spelled maxturns. Another had a model name with a stray letter on the end.

A UserPromptSubmit hook that refuses prompts containing secrets and tells Claude which branch it's on

Wed, 14 Oct 2026 07:06:00 +0000

It’s 6pm, a deploy is failing with a 403, and the fastest way to explain it to the agent is to paste the error plus the command you ran. The command has an access key in it. You hit Enter. The key is now in a request to a hosted model, in a transcript file on disk, and possibly in your prompt history.

Turn a failing deploy log into a draft incident timeline in one command

Tue, 13 Oct 2026 07:03:00 +0000

It’s 3:40pm, the error-rate alert has been quiet for nine minutes, and someone has to write the incident summary before everyone forgets what happened. The raw material is a deploy log, three alert lines, a pager acknowledgement and a git history nobody has looked at since the rollback. Assembling that into a timeline is forty minutes of copy and paste, and it’s done by the person who is most tired.

Make Claude Code interview you, then keep the editor locked until you approve the spec

Mon, 12 Oct 2026 07:06:00 +0000

The usual way an interview-first workflow fails is boring. The agent asks good questions, writes a good spec, and then the spec is a suggestion. Twenty minutes into the build it has touched a file the spec never mentioned, because it was nearby and the change looked sensible.