Git-first patch-stack porcelain
patch.moi
Maintain custom forks without hiding the work in another database.
$ patch.moi patch doctor --repo ~/workspaces/codex
base refs/remotes/upstream/main
patches 04
status ready
$ patch.moi patch rebuild --to main
pick patch/typed-run-state
pick patch/github-pages-docs
done main rebuilt from upstream + patches
One durable source
Every handoff is visible in Git.
Upstream refs, patch branches, candidate branches, forge checks, and Codex thread metadata stay where operators already inspect and recover them.
-
01
Inspect upstream
Read remote-tracking refs and release tags before mutating a fork.
-
02
Capture patches
Turn focused feature work into ordered `patch/*` branches.
-
03
Rebuild maintained branches
Replay the stack over the current upstream base with fast, auditable Git moves.
-
04
Pick up candidates
Let runners produce candidate refs while patch.moi keeps the porcelain local.
Current Tome docs
The runbooks live under `/docs`.
Start with the guide for local patch work, then move into fork maintenance, codex-toys templates, CLI reference, and the Git source-of-truth model.
Open documentationBuilt for local operators
Patch the fork. Keep the story.
patch.moi handles Git patch-stack porcelain while codex-toys and the forge own execution, retry, checks, and artifacts.
Run patch.moi locally