stacks-guard

Name: stacks-guard
Availability: InStock
Author: Stacks

Block destructive commands and require confirmation in interactive and CI sessions.

2|Updated Apr 24, 2026

Search Tags:#debugging #security #pre-commit #ci-cd #guardrails #destructive-commands #safety-rails

Ready to run

npx skills add https://github.com/stacksjs/car-rental --skill stacks-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stacks-guard
Source: https://github.com/stacksjs/car-rental/tree/main/.claude/skills/stacks-guard
Command: npx skills add https://github.com/stacksjs/car-rental --skill stacks-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent destructive actions and enforce focus during debugging sessions by automatically detecting and guarding risky commands.

Core Features & Use Cases

Destructive Command Detection: Block and require confirmation for commands that can delete data or reset environments.
Freeze Mode: Restrict edits to a defined scope and track changes during a debugging session.
Pre-Commit Safety: Scan for secrets, debugging artifacts, and large files before commits.
Activation & Usage: Use slash commands like /stacks-guard to enable guards during workflows.

Quick Start

Activate safety rails during a debugging session by issuing /stacks-guard freeze <path-pattern>.

Frequently Asked Questions about stacks-guard

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

FAQPage Schema

How do I block destructive shell commands like rm -rf or git reset --hard from executing by accident?▼

To block destructive shell commands like rm -rf, you can use safety guardrails that detect risky patterns at runtime and require explicit user confirmation before execution proceeds.

How can I restrict file edits to a specific scope while debugging to prevent unintended changes?▼

To restrict file edits during debugging, you can enable a freeze mode that limits modifications to a defined path pattern and tracks all changes within that focused scope.

How do I scan for secrets and debugging artifacts before making a git commit?▼

Pre-commit safety scans detect secrets, debugging artifacts, and large files in your staged changes, blocking the commit and warning you before any irreversible data enters the repository.

Can I enforce command safety guardrails in CI/CD pipelines and interactive sessions?▼

Yes, runtime command detection works across both interactive sessions and CI workflows, applying frontmatter-driven configuration to warn against dangerous database operations and destructive commands.

What is the best way to prevent irreversible environment resets during automated deployments?▼

The best way to prevent irreversible environment resets is implementing automated guardrails that intercept destructive commands during deployment workflows and prompt for confirmation before execution.