The CLAUDE.md at the root of that repo says, in plain English, on line eleven: never modify migration files without explicit approval. The session loads the file. Claude reads the rule. Claude modifies a migration file fourteen minutes later.
What the field is teaching, and where it stops
I went back through the most-trafficked CLAUDE.md articles on Medium from the last six months. Not to dunk on anyone. To look for the gap. The advice clusters into two dominant patterns and one good outlier, and almost every new piece is a remix.
Pattern one is the personal business OS. A solo operator publishes a beautiful directory structure. There is a decisions/ folder. There is a priorities/ folder. There is a meetings/notes/ folder with date-prefixed transcripts. The author runs it for themselves and the system clearly works for them. I have read at least eight versions of this article. Every published example is one person operating on their own machine.
That was my first real session with OpenAI’s codex-plugin-cc — an official plugin, published March 30, 2026, that puts Codex directly inside Claude Code. Not a community hack. Not a bash script wrapper. OpenAI built this, packaged it as a plugin, and shipped it through Claude Code’s plugin marketplace.
Every tech outlet has already covered what it is. This article covers what to actually do with it.
What This Is (And What It Is Not)
The plugin gives you six slash commands inside Claude Code:
/codex:review — standard read-only code review of your current changes
/codex:adversarial-review — steerable review that challenges design decisions
/codex:rescue — delegates a task entirely to Codex (bug investigation, fixes, parallel work)
/codex:status, /codex:result, /codex:cancel — job management for background tasks
It also includes an optional review gate — a Stop hook that intercepts Claude’s output and runs a Codex review before Claude can finish. More on that in Use Case 3.