What is Krites?
Krites is a free Claude Code plugin that checks a repository’s own commands when a coding agent tries to stop, rather than relying on the agent’s account of whether tests passed. It is for people who use Claude Code to change code and want a record of which checks ran and what they returned. Krites also guards selected repository paths and produces signed run receipts that can be verified offline. It requires Claude Code and Node 20 or later.
Krites Features:
Stop-Time Checks: When the agent tries to stop, Krites runs the configured checks in order and blocks the stop if a check fails, returning the failed command and its last 60 lines.
Protected Path Rules: A krites.toml file lets you name protected paths where edit tools are denied before writing, while krites.toml, .krites, and .git are always protected.
Commit Gate: For agent commits made through Bash or PowerShell, Krites checks that the latest run passed on the current changes and that the commit includes them.
Signed Run Receipts: The receipt command exports the latest run as signed JSON and Markdown, including commands, exit codes, changed files, and the commit.
Offline Verification: A dependency-free verifier lets anyone check a receipt offline using its key fingerprint.
Repository Setup: The init command can propose a krites.toml for a repository, and the configuration supports check commands, timeouts, protected-path globs, and a limit on blocked stops.
Krites Benefits:
Clear Test Evidence: You can distinguish a run that actually passed from an agent’s unverified claim, and share a record of the result with reviewers.
Fewer Manual Checks: Checks run as part of the agent’s stop attempt, reducing the need to remember to ask for a test run before reviewing its work.
Protected Test Integrity: Guarding test files and configuration makes it harder for an agent to alter the rules used to assess its own changes.
More Informed Reviews: Commands and exit codes give reviewers concrete information about what ran, without implying that the checks themselves are comprehensive.
Use Cases:
Claude Code Changes: Use Krites when Claude Code is editing a repository and you want its configured checks to run before the agent ends its work.
Protected Test Suites: Protect a repository’s test paths when an agent is changing application code and should not edit the tests used to check that work.
Agent Commits: Gate commits made by the agent so changes are checked and included in the commit before it proceeds.
Pull Request Evidence: Attach a signed receipt to a pull request when reviewers need to see which commands ran and the exit codes they returned.

