code-conductor

code-conductor

Make Claude Code work like a senior engineer, not an enthusiastic intern.

code-conductor is a drop-in governance layer for Claude Code: slash commands, hooks, guardrails, and a persistent memory system that turn free-form AI coding sessions into a disciplined, repeatable engineering workflow. What an agent may run is checked before it runs, what it decided is written where the next session will read it, and what shipped is asserted against the record by instruments that run in CI. It cuts token usage along the way.

One command to install: npx @yeison.restrepo.r/code-conductor@latest --project. No code changes to your project. Works with any stack. And every claim below is checkable against a commit in this repository.

Why this exists

If you have used Claude Code for more than a week, you have probably seen all of this:

- It reads entire files, or entire codebases, to answer a one-line question. Every one of those reads burns tokens and fills the context window with noise.
- It forgets everything between sessions. The conventions you explained yesterday, the architectural decision from last sprint, the workaround for that flaky test: gone. You explain them again, and pay for the tokens again.
- It starts coding before anyone agreed on *what* to build. Fast output, wrong problem, full rewrite.
- The context window fills up silently, the session auto-compacts at the worst possible moment, and the agent loses the thread mid-task.
- It overwrites files it should not, and nobody finds out until the diff.

None of these are model problems. They are *process* problems, and process is exactly what code-conductor installs.

Quickstart

Three commands, from nothing to a guarded session. The output below is real, captured by running exactly these commands in a…