Make task handoffs require a commit ID
A developer paired a YAML todo script with a Claude Code helper that fetched the next job and closed it only after a commit ID was provided.
- What they did
- They first put together a Python script to keep task items in a YAML file. After that, they added a Claude Code sub-agent to handle task flow: one step pulled the next open item, and another step recorded it as finished. To tie the process to version control, the finish step would not proceed without a commit ID.
- How it went
- The setup improved visibility into work one task at a time and helped keep commits atomic. It still had a weakness: Claude Code sometimes skipped the custom flow and fell back to TodoWrite.
- Tips
- If you build something similar, check that the agent is actually using the intended handoff instead of switching tools behind your back. The commit-ID rule helps, but it does not fully prevent bypasses.
Try it yourself with Claude Code
Create a Claude Code helper named [helper name] for [project]. Have it read open items from [task file or tracker], return the next item to work on, and only close that item after I give a commit ID. Before any irreversible step such as sending, deleting, or submitting, stop and ask for my approval. Try it on one task and show me the full handoff and closeout.
Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.
2 more reports of this
Get 3 agent uses like this every morning
With the day's top AI news. Free, and one click to unsubscribe.
Related agent uses
Flag coding conflicts before agents edit
They set up a local layer that makes coding agents announce planned changes so overlapping architecture work gets caught early.
Ask Claude Code to prototype a kernel change
Linus Torvalds had Claude Code help produce a Linux kernel patch, plus tests, review, and a first cover-letter draft.
Let Claude work from GitHub code and pause before posting
A commenter gives Claude source code and a feature brief, then reviews the draft only when PR review begins.
Use Claude Code to maintain NixOS server configs
A developer uses Claude Code to edit one NixOS config repo for several self-hosted machines, then reviews the diff and applies changes by hand.
Move Claude Code skills into Codex
Charlie Hills used Claude Code and Codex to migrate 201 skills in an afternoon, then checked which parts worked in both tools and which still needed fixes.
Set up a separate sandbox QA pass
Codex turned an existing Claude login into a second reviewer that checked an AI system without changing the user’s credentials.