oc-approve

A human-in-the-loop approval gate requires explicit user consent before executing destructive shell commands. You queue an approval request for the dangerous operation and await the user's decision, with the system managing pending approvals, denials, and expirations.

Gating destructive git operations with a human-in-the-loop approval prevents unintended actions triggered from web-chat. The system restricts risky actions to allowed channels and requires explicit consent before executing file deletions or git commands.

Yes, you can manage multi-step approval chains with pending approvals and timeouts. The workflow support handles single gates and sequential chains, tracking completion status, timeouts, and expirations to ensure safe execution of destructive operations.

The approval mechanism works for external API calls and file deletions. Designed for web-chat initiated commands and high-risk tasks, it requires human consent before any destructive file operations, external API calls, or shell commands proceed.

A specific YAML frontmatter format is required to configure the approval workflow. The Skill enforces a frontmatter containing name and description fields, and supports optional scripts, references, and assets for managing the approval gate.