Back to list

Genesis

An agent skill that draws your codebase as a business flow map and shows which of your agent's changes are untested or risky.

小桃拍两张
Author
@小桃拍两张
Project ShowcaseDeveloper ToolsOnlineclaude-codecodex
0
0

Project intro

Genesis is an agent skill for Claude Code and Codex that turns your codebase into a business flow map and shows which of your agent's changes are untested or risky. You run /genesis map to draw the system as it is now, or /genesis review main to see what changed since a revision and whether a test checks each change, then open the result in a browser or paste the summary into a pull request.

The pain is familiar to anyone who lets an agent loose on a codebase: it builds what you asked for and quietly changes three other things on the way, and you cannot tell which of those changes a test would actually catch. Genesis puts every change on the flow — a card charge retried without an idempotency key, stock no longer held while the card is charged, guest checkout, a free-shipping threshold moved from $50 to $35 — and gives each one a verdict: covered, reached only, unknown, or not reached at all.

It does not take the agent's word for it: every step the agent writes has to quote the lines of code it stands for, and the Genesis CLI checks each quote against a frozen snapshot of the repo, rejecting the whole description if one does not match. For Python it also parses the code itself, so a branch the agent skips leaves the map marked partial. In the authors' own benchmark, 10 commits from 5 open-source Python repos, correct test-coverage verdicts rose from 79% to 88% for Claude Code and 76% to 80% for Codex. It has 52 stars on GitHub with 8 forks, 122 commits, and was pushed on 18 November 2026.

Two honest limits: Python gets the most accurate results, because that is the language Genesis parses; other languages work through the agent reading the code, and a path the agent misses is not flagged. And the verdicts come from reading your tests — Genesis does not run them — while risks are only what your agent noticed, with no rule engine behind them. The CLI itself calls no model, sends nothing anywhere, and never runs your code.

Actions

Visit project URL

Tech stack

python

Project info

Project category
Developer Tools
Project status
Online
Collaboration intent
None

Comments (0)

ME
0/1000
Loading comments...