pi-gatekeeper
Done means the checks pass.
Coding agents can make a plausible change and declare victory before the tests or typechecker agree. pi-gatekeeper puts a verification step between the edit and the finish line.
View the repository on GitHub ↗A feedback loop for finishing
When Pi is about to finish after a task that may have changed something, the extension runs your check command. If it fails, the output is fed back to the agent so it can investigate and try again. Repeated identical failures prompt a change of approach, and an attempt limit prevents the loop from running forever.
Your project, your checks
Set PI_GATEKEEPER_CHECK to the command you want to run, or let the extension find a check script in your package.json. If neither is available, the gate stays idle rather than guessing. The/gate commands let you check its status or run verification yourself.
An optional rollback can restore tracked files to their pre-task state after repeated failures. It is off by default: rollback can also undo manual edits, and it does not remove untracked files.
Try it with Pi
Install the extension from npm, then choose a non-interactive check that suits your project.
pi install npm:pi-gatekeeper