stop-me-check
Installation
SKILL.md
stop-me-check
Run the stop-me gates backwards over code that already exists. Report only what would have failed all three.
Method
- Read
.stop-me.ymlif present, else inferhorizonfrom the repo (deploy targets, tenancy columns, contributor count) and say which you assumed. - Read
DECISIONS.mdif present. Anything already logged there is settled — never report it. - Sweep the irreversible surfaces from the stop-me skill — that list lives there and only there; never keep a second copy here. For each, gather evidence before you claim anything:
migrations/— drops, renames, narrowing types, missing down-path- money paths — charge/refund/quota, and whether an idempotency key and a test exist
- secrets — literals in tracked files;
git log -Sfor the commit that introduced them - auth — password hashing, token expiry, permission checks on write paths
- tenancy — tables missing a tenant column that siblings have
- published shapes — unversioned endpoints,
anyon exported types, CLI flags - deletes —
DELETE/drop/rm -rfwithout a restore path - data not collected — events and audit rows with no actor or timestamp
- Rank by blast radius, not by count.