stacks-guard

Intercept and validate destructive shell commands and file operations in development environments.

2|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/bughq/bughq --skill stacks-guard-bughq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacks-guard
Source: https://github.com/bughq/bughq/tree/main/.claude/skills/stacks-guard
Command: npx skills add https://github.com/bughq/bughq --skill stacks-guard-bughq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents accidental execution of destructive commands and enforces focus during debugging sessions by providing a protective layer over your terminal environment.

Core Features & Use Cases

  • Destructive Command Detection: Automatically blocks or warns against dangerous operations like database drops, forced git pushes, or recursive file deletions.
  • Freeze Mode: Restricts file edits to a specific scope during intense debugging to prevent accidental changes to unrelated files.
  • Pre-Commit Safety: Scans for secrets, debug artifacts, and large files before you commit code to your repository.

Quick Start

Invoke the stacks-guard skill by typing /stacks-guard followed by your desired command or the freeze keyword to initiate a protected debugging session.

Frequently Asked Questions about stacks-guard

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

FAQPage Schema
How do I prevent accidental destructive shell commands during development?

Preventing destructive shell commands requires a safety monitoring layer that intercepts and validates operations. This Skill blocks dangerous commands like recursive file deletions and database drops before execution in your local environment.

How do I restrict file edits to a specific scope while debugging?

Restricting file edits during debugging is achieved using Freeze Mode. This feature limits modifications to a defined scope, preventing accidental changes to unrelated files during intense debugging sessions.

Can I scan for secrets and debug artifacts before a git commit?

Scanning for secrets before a git commit is supported through Pre-Commit Safety. It automatically checks your code for sensitive data, debug artifacts, and large files prior to committing to your repository.

Does this command safety guardrail require shell environment integration?

Command safety guardrails require direct integration with your local shell environment. This setup allows the monitoring layer to effectively intercept command execution and validate file system modifications.

What is the best way to block forced git pushes automatically?

Blocking forced git pushes is handled by Destructive Command Detection. It automatically identifies and warns against dangerous operations, including forced pushes and recursive deletions, within your development workflow.