permission-guard

Requiring explicit approval for destructive bash commands involves halting execution before risky actions and prompting for user consent. This skill enforces a protocol that requests permission, explains the scope, and handles approvals for CI/CD pipelines and automation.

Preventing AI copilots from executing destructive file operations requires a guardrail that forces a halt before risky changes. This skill intercepts destructive actions, providing a precise impact list and demanding explicit consent before proceeding.

Gating system config edits and credential changes during automation requires pausing operations to request explicit permission. This skill enforces a strict protocol across development and deployment workflows, demanding a rationale and approval prompt before executing irreversible edits.

Yes, you can integrate a safety guard for destructive ops into existing automation runtimes. This skill works across development, deployment, and automation workflows to pause destructive commands, explain the scope, and require explicit user approval before proceeding.

When halting destructive operations for explicit permission, the limitation is that execution stops entirely until approval is granted. This safety mechanism requires a rationale, a precise impact list, and an explicit approval prompt, which may interrupt automated workflow continuity.