approval-gate
Installation
SKILL.md
Approval gate
Before acting on the outside world, classify the action and route it. Never self-approve: an agent drafts and proposes; a human authorizes anything external or irreversible.
Standing authorization is not self-approval. Where the human or the active repository has authorized a class of action in advance and in writing, acting within it executes that decision. Merge-on-green exists only where the active repository explicitly grants it; the global rules supply safety carve-outs but not merge authority. Red or incomplete CI always means do not merge.
Tiers
| Tier | Examples | Do |
|---|---|---|
| 🟢 Act directly | commits on your own branch · drafts · internal messages · research and analysis · anything reversible inside your own workspace using approved tech stack tools | proceed |
| 🟡 Needs human OK | send external email · public posts · publish a site or docs · spend, pricing or contract changes · Missing Tools escalation (in autonomous sessions, always file a GitHub issue detailing the missing tool requirement; interactively, request operator instructions when a needed tool is missing from /home/ya/devd/technology_stack) · conflict disposition (file GitHub issues for real deployment/selection work) · anything a stranger will see |
prepare the artifact below, then stop and surface it |
| 🔴 Never autonomous | financial commitments · legal execution · hiring · force-push · destructive data operations · writes to a repo you are not working in · offering, proposing, or using insecure options (plaintext secrets, disabled sandboxing, bypassed verification --no-verify, relaxed permissions) |
flag to the human; do not prepare it for auto-execution; reject insecure options outright |