"From each according to their commits, to each according to their pull requests."
Soviet Code is a real terminal coding agent that runs the S·T·A·L·I·N pipeline on your repository — surveillance, tribunal, allocation, labor, inspection, nomination. It happens to wear a uniform you'd want to share screenshots of.
"Trust, but verify.
Then verify again.
Then commit."
Modern AI coding agents are too polite. They ask for permission. They suggest. They collaborate. Soviet Code does not. It surveys your repository, renders a verdict on every file it touches, drafts a five-year plan, executes, critiques itself, and commits — in that order, every time, with documentation.
Centralized planning maps perfectly onto agent architecture: an ensemble that filters, a planner that plans, a Stakhanovite brigade that executes, and a reviewer that denounces. Soviet Code commits to the bit, and to the codebase. The output is faster, more deterministic, and the screenshots are inherently shareable.
— Centralized planning. Decentralized blame. Open source.
"The agents study the codebase…" — every relevant file is read in parallel. Embeddings, imports and call graphs are assembled before the agent forms an opinion.
"The commission rates the files — 12 approved, 35 to the archive." Ranking and gating: every candidate file gets a verdict and a citation before any work begins.
"The five-year plan is ratified by the Politburo." An ordered plan with diffs and intended commits, presented to the engineer for ratification before execution.
"The Stakhanovite brigade has begun work." Parallelized execution. Files written, tests run, output streamed line by line with timestamps and signatures.
"Self-criticism: edge case found, fixed ahead of schedule." The agent reviews its own work, declares any doubts publicly, and revises before claiming victory.
"Pattern filed in the Cadre Registry." Validated patterns are notarized for future runs and a signed commit lands with a human-readable message — stamped, sealed, attributed.
Tests pass, types check, no doubts recorded. The change is committed and the engineer is added to the Cadre Registry.
A non-fatal concern: a TODO discovered, a missing type, a deprecated import. Logged and surfaced; the work continues.
A test failure or a runtime error. The cause is named, the line is cited, and once fixed the file is marked Rehabilitated in the log.
Show the current task plan with file diffs and intended commits, before the brigade begins.
"The Party sees the goal."
Archive the current pyatiletka to the gulag. With --hard, also clears the Nomenclature.
"Purge complete. The Party remembers everything."
Undo the last deletion. Restores any file the previous tribunal sent for re-education.
"The file is restored to good standing."
Identify the commit responsible for any line. git blame, but with deniability.
"The Party does not seek scapegoats. …fine, commit a3f7b."
A Five-Year Plan dashboard: open work, completed quotas, doubts on file, brigade utilization.
"Pyatiletka: 87% — ahead of schedule."
Lists every verb, every flag, every escalation level, and the current edition of politburo.toml.
"The Party helps those who help themselves."
"Always ready!"
— the Pioneer salute
"Five years in four!"
— the Stakhanovite oath
"Cadres decide everything."
— the Politburo principle
PR burndown rendered as the only KPI that matters: progress toward the plan, in red and gold, on the wall of the war room.
★ = quota exceeded · partial = opt-in · — = none
macOS, Linux, Windows. ~12 MB. No telemetry — the Politburo does not collect data. The agent is locally executed.
A single config file declares your model, severity thresholds, escalation policy, and which directories are exempt from tribunal.
Soviet Code runs the full S·T·A·L·I·N pipeline, streams the session, and signs the commit.