Imported from aliatx2017/reasonix-hermes (
.reasonix/skills/pre-action-gate/SKILL.md). Install upstream withnpx skills add aliatx2017/reasonix-hermes --skill pre-action-gate. Copyright stays with the author.
Pre-Action Gate
Load before any write, edit, or deploy. This is a gate — it doesn't produce output; it blocks premature moves.
The gate
Before any file mutation — re-read the target area. Code drifts between reads; stale context is the #1 cause of garbled edits. Use content_hash on edit_file whenever you touch a file.
After any change — go build ./... must pass before you call the step done. Not "should pass," not "probably passes" — you run it and show the output. One change → one build. Iterate.
Before claiming completion — evidence must be in the same response as the claim. complete_step enforces this structurally: the host rejects completions without verification commands. Don't fight it — feed it.
What this gate replaces
This skill encodes three constitution rules into one behavioral checkpoint. Load it instead of consulting the constitution directly — it's the distilled form:
go-vet-clean→ build chain checksubstantiate-every-claim→ evidence-before-claimnever-say-fixed→ only the user declares fixed
Failure modes
- Stale edit — file changed since last read → garbled code. Re-read every time.
- Premature "done" — claiming completion without build output. The host blocks it; don't waste the turn.
- Batch-and-pray — 10 edits, then one build. One edit → one build.
multi_editfor single-file batches only.
Related
ready-means-tested— evidence gate for status claimsevidence-first-reasoning— diagnostic verification under ambiguity- Constitution:
.reasonix/constitution.json