gstack-guard

Enforce destructive-command warnings and directory-scoped edit boundaries.

1|1|Updated Mar 5, 2026

Search Tags:#automation #production #safety #guard #destructive-warnings #edit-boundary

Ready to run

npx skills add https://github.com/tan-yong-sheng/GrowChat --skill gstack-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack-guard
Source: https://github.com/tan-yong-sheng/GrowChat/tree/main/.claude/skills/gstack-guard
Command: npx skills add https://github.com/tan-yong-sheng/GrowChat --skill gstack-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Protect live systems by enforcing destructive-command warnings and directory-scoped edit boundaries.

Core Features & Use Cases

Destructive command warnings: detects and warns on commands like rm -rf, DROP TABLE, force-push, etc.
Directory-boundary edits: ensures edits are restricted to a user-specified path to prevent accidental modifications outside scope.
Safe-guarded integration: combines careful and freeze workflows to provide maximum protection during prod debugging or high-risk changes.

Quick Start

Provide a target directory to restrict edits to, then enable guard mode to activate destructive-command warnings and edit boundaries.

Frequently Asked Questions about gstack-guard

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

FAQPage Schema

How do I prevent accidental destructive commands in production environments?▼

To prevent accidental destructive commands in production, you need a safety guardrail that detects and warns on high-risk commands like rm -rf, DROP TABLE, and force-push before they execute.

Can I restrict code edits to a specific directory boundary?▼

Yes, you can restrict code edits to a specific directory boundary by providing a target directory path, ensuring modifications are confined and preventing accidental changes outside the designated scope.

What is directory-scoped edit boundary enforcement for sensitive configurations?▼

Directory-scoped edit boundary enforcement is a safety mechanism that confines code and configuration modifications to a user-specified path, preventing unauthorized or accidental alterations to files outside that boundary.

How do I set up safety guardrails for high-risk production debugging?▼

To set up safety guardrails for high-risk production debugging, provide a target directory to restrict edits and enable guard mode to activate destructive-command warnings and directory boundaries.

Does the careful and freeze workflow integrate with edit boundary enforcement?▼

Yes, the careful and freeze workflows integrate with edit boundary enforcement and destructive-command warnings to provide maximum protection during sensitive modifications and production debugging.

When should I not use automated destructive-command warnings?▼

You should not rely solely on destructive-command warnings when executing fully automated, non-interactive scripts where user prompts cannot be answered, as the safety guardrails expect human intervention to proceed.