I built an OSS tool called markgate that mechanically catches and enforces two kinds of gaps: when a Coding Agent (Claude Code, etc.) accidentally forgets to call a Skill that runs build or tests after implementation and commits anyway, and when AI tasks that can't be reduced to a command — like a /check-docs Skill — can't be enforced through hooks.
markgate
NOTE: markgate is meant to run inside a git repository.
markgate
markgate is a CLI tool that acts as an enforcement layer wedged between the Coding Agent and your hooks . By mechanically catching and enforcing the Coding Agent's mistakes and omissions, it addresses the following three failure patterns.
Pattern Failure pattern it addresses Solution
1 Catching forgotten calls and avoiding duplicate execution markgate run
2 Enforcing non-command tasks markgate set + markgate verify
3 Scoping multiple tasks + aggregate verify composes in .markgate.yml
Below, we'll walk through each pattern in turn.
Pattern 1: Catching Forgotten Calls and Avoiding…