Block destructive commands and require confirmation in interactive and CI sessions.
npx skills add https://github.com/stacksjs/car-rental --skill stacks-guard
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
Prevent destructive actions and enforce focus during debugging sessions by automatically detecting and guarding risky commands.
Activate safety rails during a debugging session by issuing /stacks-guard freeze <path-pattern>.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
steadyfallIntercept destructive shell commands with a PreToolUse hook to warn before execution.
duonghuan2122000Automatically commit changes after Spec Kit hooks when auto-commit is enabled.
piotrbDetect unencrypted secret files in staged Git changes and block commits.
martin-hsu-testIntercept risky shell commands and prompt for confirmation before destructive actions.
