Capture the decision
Plan approval can snapshot the decision. The installed post-commit hook joins changed files to the approved plan and records available reasons and rule references.
Writ by Infinri
Keep the reasons behind the code
Writ links approved plans, commits and recorded file-change reasons, then brings selected decisions into later Claude Code sessions through Recall.
ApproveRecord the plan
→ CommitLink changed files
→ RecallRead the reasons
Keep it with the project
Decision records are project-scoped. Git notes on refs/notes/writ-decisions provide another way to read recorded reasons alongside commits.
Bring it back when relevant
Recall selects records using named paths and matching terms. The first briefing of an epoch can fill with recent decisions. Later prompts show unseen matches.
How can I inspect a record?
After installing Writ and capturing a commit in a disposable project, inspect the available decisions:
writ recall --repo . --full --limit 5This is a command to try, not output from a run performed for this page. A new install may have no records yet.
Is this a complete chat history?
No. Decision memory is built from plans and commits. The auto-memory mirror holds each memory's latest contents, not its history. Compaction handoff is best effort.
Does a record prove the rules were followed?
No. It records what the agent was shown and what it claimed to apply. You still review the diff and tests. Capture can fail when the local service is unavailable, and the post-commit hook does not block a commit.
Can it post reasons to a pull request?
Optional writ pr sync supports Bitbucket Cloud. It does not provide GitHub pull request sync. Review the security model before enabling an outbound integration.