Your PR Says the Tests Passed. Prove It. - Stephen Chin & Cassandra Chin

A pull request can claim that checks passed even when the recorded commands do not establish that the submitted change was tested. Cassandra Chin built Tracetoon to recover the context behind a branch, write a better pull request description and optionally explain it with a comic. Together with Stephen Chin, she follows one troublesome review through repeated revisions, missing evidence and rising token costs. The problem is more specific than producing fluent prose: the writer needs to connect a change to its rationale, the commands that ran, their timing and the version of the code they actually checked. Their next iteration uses Relate, an embedded graph database written in Rust, to assemble that evidence before the writing begins. A connected brief gives the writer and reviewers the same sources, reducing repeated searches through session logs. The speakers explain why they kept a stronger writer while using less expensive reviewers to check claims against the brief, and show results from their own PR Bench development comparisons. Those reported results combine improved description quality with roughly half the token usage; they describe this project's evaluation, not a guarantee for other codebases. The practical pattern is to preserve provenance and relationships outside the model's conversation, make uncertainty visible, and give reviewers evidence tied to the submitted content. The comic provides the story, but the useful engineering artifact is the reviewable chain behind each claim. Speaker info: Stephen Chin, Neo4j - https://github.com/steveonjava Cassandra Chin, Tracetoon creator - https://www.linkedin.com/in/cassandra-chin-developer Project: - https://tracetoon.com/ Timestamps: 0:00 - Why Cassandra built Tracetoon 1:40 - A pull request enters the token factory 4:35 - Recovering evidence across agent sessions 7:35 - The original Tracetoon research and review loop 9:10 - When a passing check claim lacks evidence 10:25 - Why cheaper writers did not solve the problem 11:15 - Introducing the Relate evidence graph 13:28 - Connected briefs and focused reviewers 15:24 - Tying claims to the submitted change 16:26 - PR Bench results and token usage 19:46 - Lessons, project links and closing remarks