The problem Codebases drift from what their docs say, and three moments cost developers the most time. The README documents /api/v2 while the server runs /api/v1, and a new contributor loses an afternoon. A stack trace arrives from production with no repro, and someone greps for an hour. A dependency bump looks like one line, then CI turns red. AI coding tools help with the file you have open; they don't check docs, code, tests and dependencies together, or leave proof of what they found. The solution TriRepo is a three-check clinic for one codebase: one repo in, three truths out. - Lies finds where the documentation contradicts the code. - Crash turns a stack trace into the failing line, a cause and a fix. - Bump shows what breaks in this repo if you upgrade a dependency. Each check works at two depths. The deep pass is IBM Bob 2.0. On a sample invoice API with planted problems, Bob ran each check as its own Ask → Plan → Agent task. For Lies, two subagents read the docs and the code independently, and Bob found 11 contradictions, including two nobody planted, fixing three. For Crash, Bob started from the raw trace alone, wrote a failing test, fixed the code and confirmed 35 of 35 tests green. For Bump, Bob installed Express 5, reproduced four real breaks rather than guessing, patched three and documented the fourth as residual risk. 13 session screenshots record every step, and an answer key, written after the passes, compares Bob's findings with what was planted. The live pass works on any public GitHub repo, in the browser, in seconds, with no signup and no AI. Paste a URL and TriRepo checks script names, Node versions and ports against package.json; opens the failing line of any Node, Python, Java, Go or Ruby trace on GitHub and points at the likely culprit; and flags every dependency a major version behind, then lists each file and line that imports it. Who it's for Maintainers inheriting a repo, on-call engineers holding a stack trace, and teams planning an upgrade. They start on the landing page, paste a repo, and move between three tabs. Bob's deep pass loads in one click. What makes it different Three checks share one repo, one interface and one standard of evidence: every finding points to a file and line, and TriRepo says when it can't check something instead of guessing. Bob's passes prove problems before claiming them, with a red test and a real crash. The live checks make it usable on any repo today; the deep pass shows how far full-repo context goes. Credits Bob built the sample app, all three deep analyses, every fix, the prompts and the original UI with its live Lies check. After the Bob allowance ran out, the live Crash and Bump tools, the landing page and the visual design were added with Claude Code; the repo lists exactly which files.
Category tags: