Local-first change review
Changeproof binds the requirement, baseline, and responsibility before work begins. After the change, the CLI connects the diff, tests, and open risks in a signed Change Passport. Existing changes can be inspected retrospectively.
Two paths to evidence
Both paths create a Change Passport. They make different claims about what was actually observed while the change was produced.
start → finishStrongest evidenceChangeproof starts before the first edit. Intent, Git baseline, the stated agent, and the responsible human are bound at that point.
The passport can show where the run started and which change emerged before it was finished.
inspectRetrospectiveAn existing commit or Git range is analyzed together with a ticket or specification. Files, tests, dependencies, and risks are connected afterwards.
The passport describes visible evidence without claiming AI authorship that was not observed at the time.
Observed run
A complete run creates a verifiable chain from business intent to the sealed result without replacing the engineering work itself.
A ticket or specification describes the intended change and its verifiable criteria.
Changeproof hashes the requirement and records the baseline, agent, and responsible sponsor before the change.
changeproof start --intent ticket.md --agent codex --sponsor youHuman and agent work in the repository. Git remains the source for files and structure; claims retain their evidence level.
The diff and tests are evaluated, open risks remain visible, and the Change Passport is signed.
changeproof finish --test "npm test" --openSchema, digest, and signature can be checked again independently from the HTML presentation.
changeproof verify passport.jsonThe Change Passport
The passport does more than collect metrics. It records where every claim comes from and which business criteria already have supporting evidence.
intentSource, hash, summary, and extracted acceptance criteria.
changeGit range, files, line counts, categories, and structural relationships.
testExecuted command, result, changed test files, and output digest.
riskFindings for migrations, APIs, privacy, or automation linked to their sources.
integrityMachine-readable JSON, SHA-256 digest, and Ed25519 signature.
Where it helps
Intent and human responsibility remain connected to the resulting diff.
Data model, API surface, tests, and open risks become visible in one handover artifact.
An existing Git range can be inspected retrospectively against a ticket or specification.
Reviewers see scope, evidence, and gaps before drilling into individual files.
Runs locally
Source code and prompts stay on the developer's machine. After a local build, both workflows are available through the same CLI.
One-time setup
git clone https://github.com/entwicklerherz/changeproof.gitcd changeproof && npm install && npm run buildObserved run
npm exec changeproof -- start --intent ticket.md --agent codex --sponsor younpm exec changeproof -- finish --test "npm test" --openExisting change
npm exec changeproof -- inspect HEAD~1..HEAD --intent ticket.md --test "npm test" --openLab prototype · Not yet published to the public npm registry · Run through npm exec after a local build.
Source code and guide on GitHub