Behavior-driven development
Keep your coding agent from undoing your fixes
Save the requirement as a rule. Check later edits for the bug you already fixed.
Perch / Examples
Catch regressions, enforce project rules, and check the code and documentation your agent changes.
Behavior-driven development
Save the requirement as a rule. Check later edits for the bug you already fixed.
Scan types
Choose defect, security, and saved-rule checks when reviewing generated code, then inspect the agent's changes against a base commit.
Defects
Scan generated code for broken behavior, then check the fix before committing.
Security
Require an ownership check and recheck it after the agent changes the handler.
Security
Check that private routes still require authentication and records still require permission.
Behavior-driven development
Require the same validation after a rewrite, even when the generated code takes a different approach.
Documentation
Catch vague headings, filler paragraphs, and examples with no output before the agent finishes.
Code comments
Check the promises in an agent’s comments against return values, errors, and side effects.
Behavior-driven development
Run Perch against working files, save a named rule in perch.yaml, configure Claude Code, Codex or Cursor, and repeat the same check after a repair.