permission-guard

Require explicit approval before executing destructive file, credential, or system operations.

3|Updated Apr 1, 2026

Search Tags:#bash #safety #credentials #approval #permission #guard #destructive-ops

Ready to run

npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill permission-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: permission-guard
Source: https://github.com/vtgiang-dotcom/Solo-Code-Harness/tree/main/.gemini/antigravity/skills/permission-guard
Command: npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill permission-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill protects environments from destructive, dangerous, or irreversible operations by forcing explicit permission before deletion, credential changes, or system-wide edits, ensuring safer automation.

Core Features & Use Cases

Pauses destructive commands and prompts for explicit consent before proceeding.
Enforces a protocol for permission requests, scope explanations, and approval handling.
Useful for CI/CD pipelines, AI copilots, and automation runtimes that may attempt risky changes.

Quick Start

Halt before any destructive action and ask the AI to request explicit user approval with a clear scope.

Frequently Asked Questions about permission-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I require explicit approval before running destructive bash commands in CI/CD pipelines?▼

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.

What is the best way to prevent AI copilots from executing destructive file operations without permission?▼

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.

How do I gate system config edits and credential changes during automation workflows?▼

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.

Can I integrate a safety guard for destructive ops into my existing automation runtime?▼

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.

What limitations should I expect when halting destructive operations for explicit permission?▼

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.