Let Claude Code, Codex, and Grok Bot share one set of notes in git

The scene

The same project is handed between several coding agents, and you want conventions, recent decisions, and unfinished work in one place instead of scattered chats.

Tools involved

What they did

1. Agree on a place and format for shared notes in the repo — conventions, recent decisions, unfinished work — and keep them under version control.
2. Give every agent the same starting rule: read and follow those files before touching code.
3. When a session ends, write decisions and leftover work back to the same files in one clear commit, and leave unrelated files alone.
4. Never commit secrets, passwords, or private customer data. New models should still read the same notes.

Copyable prompt

Before you start, read the shared notes in this repository and follow them. When you finish, commit your decisions and anything still open back to those same files in a single commit. Do not change unrelated files, and never write secrets into the repo.

Rewritten here for you to try; not a verbatim excerpt from elsewhere. What it asks：Rewritten here from the read-then-write-back method, ready to paste into each agent that joins the handoff.

Things to watch

This is a public method write-up, not a verbatim prompt the author typed. Messy notes make messy handoffs. You need coding agents that can read and write the repo. Generally reproducible in China, depending on which model services you use.

A coding-agent subscription that can work in a git repo, such as Claude Code, Codex, or Grok Bot.

Reusable templates

Before you start, read and follow the shared notes in this repository (conventions, recent decisions, unfinished work). When you finish, commit what you decided and what is still open. Leave unrelated files alone, and never commit secrets.