Quick start
Habits that keep agent work reviewable
Factimonious narrates what landed in the repository. These rules make coding agents leave clearer evidence—so standups, retros, and humans can trust the trail. Copy into AGENTS.md, Cursor rules, or team agent instructions.
Rules
Three rules
Git commits
Add a line to your AGENTS.md (or team agent instructions) like:
Git commits: Always include: [FEATURE/BUG-xxx] + one-line behavior change + evidence files + "why it matters" intent.
Claims and conclusions
Keep agents grounded in repository facts:
When you state a conclusion, cite the file path (and line range or commit) it came from; if you cannot cite evidence, say what is unknown.
Wrapping up a task
Make completion auditable for standups and retros:
Before marking work complete: run the relevant tests or build, note the command, and summarize pass/fail with a short excerpt from the output.
Paste
Drop-in AGENTS.md block
Optional combined snippet for teams that want one paste.
## Evidence-first agent habits (Factimonious-aligned) Git commits: Always include: [FEATURE/BUG-xxx] + one-line behavior change + evidence files + "why it matters" intent. When you state a conclusion, cite the file path (and line range or commit) it came from; if you cannot cite evidence, say what is unknown. Before marking work complete: run the relevant tests or build, note the command, and summarize pass/fail with a short excerpt from the output.
Factimonious reads commits, diffs, PRs, and workflow signals. Agents that invent ungrounded status, skip tests, or write decorative commit messages create narrative theater upstream. These habits shrink that gap before analysis runs.