Guard a session
Rank the dirty files that can actually hurt, so you read the 3% first.
After a vibecode session, do not read twenty files in git order. Read the two that can break the most.
guard_session looks at this session’s dirty files — the working tree
minus anything you already had dirty when the work started — and ranks them
by blast risk. High-blast hunks first. Flags on duplicates, orphans, and
package-boundary crossings.
Guard is an MCP / IDE panel. From a script, roll up the dirty tree with review; then ask the agent for Guard’s read-first ranking.
prism reviewWhat you get back
| Check | Meaning |
|---|---|
| Blast rank | Changed paths sorted so the highest-risk file is first |
| Duplicate | A new symbol that looks like one that already exists |
| Orphan | A new file nothing imports yet |
| Boundary | A change that crossed a package or DNA boundary |
The session is:
git dirty paths − preExistingChangesThat subtract is why a teammate’s review does not drown in files you already had open.
When to use it
- After you (or a teammate) touched many files and you do not know where to start reading.
- Before you land uncommitted work — pair with Review a PR.
- After a finding job: Guard the job’s files, not the whole dirty tree.
When this is wrong
- Guard does not say the edit is correct. It says which files can hurt.
- Files you pass as
preExistingChangesare excluded on purpose. - Blast is a floor: dynamic imports and runtime DI are invisible. See Before you edit.