tessri.

Which command, when

Every command is one view of the same picture of the code and its history, so the question is only which moment you are at. The MCP tool is the same question for an agent that speaks the protocol; it returns the command's JSON and its text from one analysis.

MomentCommandMCP toolRead first
Getting to know a repositorytessri scan ., or --format html --out report.html for the explorertessri_scanthe summary, the per-directory table, then caveats
About to change a file or directorytessri impact <path>tessri_impactthe dependents and the tests that reach it, then the owners
Checking a claim about one filetessri why <path>tessri_whythe verdict and the evidence lines under it
Planning a cleanup, or reading the structuretessri graph .tessri_graphthe cycles, then the few dependencies to cut
Reviewing a changetessri triage --since <base>tessri_triagethe first rows and why they are first, then who can look
When a change is donetessri check --since <base>tessri_checkthe findings by severity; --fail-on turns a severity into an exit code
Handing a change to a persontessri brief --since <base> --ran "<check: result>"tessri_briefthe scope line, then the look-first table, then what is open for a person
On every pull requesttessri integration install --agent reviewthe comment on the pull request, updated on every push
Weeklytessri integration install --agent reportthe run's summary; the JSON and the HTML page are its artifact
Giving it to an agenttessri integration install --agent claude (or codex, agents, copilot, mcp, vscode)tessri integration status, which says per host what it has and what is left
While an agent editstessri integration install --agent claude-hooks (or codex-hooks)what the edited file reaches, after each edit; what the uncommitted work did to the structure, when the agent stops (hooks)

Three things hold across the table. Without --since, a branch is judged against the default branch (the one the remote declares, else main or master); on the default branch itself the change is the uncommitted work, and --since HEAD means that anywhere. Every command takes the repository root as --repo PATH, and scan and graph also as their first argument. And the command line, the MCP tool and the JSON say the same thing in the same words: --format json is the same facts as data, with the meta block that says exactly what was analysed.

Ownership and review load have no command of their own: they are sections of scan (the ownership and review load pages), and why shows one file's maintainers with the rest of its evidence.

Source: docs/guide/when.md, Markdown in the repository; this page is built from it. Edit it on GitHub.