guard

Warn on destructive commands and restrict edits to a specified directory.

Updated May 11, 2026
One-click install
npx skills add https://github.com/wodeh/gstack-kimi --skill guard-wodeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/wodeh/gstack-kimi/tree/main/guard
Command: npx skills add https://github.com/wodeh/gstack-kimi --skill guard-wodeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full safety mode: destructive command warnings + directory-scoped edits. Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems. Use when asked to "guard mode", "full safety", "lock it down", or "maximum safety".

Core Features & Use Cases

  • Destructive command warnings are always on to prevent accidental data loss.
  • Directory-based edit freeze ensures edits are restricted to a safe path during maintenance or debugging.
  • Quick adoption with clear setup steps and integration with existing care/freeze components for safe operations.

Quick Start

Invoke guard mode to enable destructive-command warnings and a boundary-restricted editing environment.

Frequently Asked Questions about guard

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

FAQPage Schema
How do I prevent accidental destructive commands like rm -rf or force-push during prod maintenance?

To prevent destructive commands during prod maintenance, enable a full safety mode that automatically warns before executing risky operations like rm -rf, DROP TABLE, or force-push. This ensures maximum safety when touching live systems.

Can I restrict file edits to a specific directory boundary while debugging?

Yes, you can restrict file edits to a specific directory boundary by applying an edit freeze. This blocks any modifications outside the specified safe path, ensuring debugging sessions remain isolated and controlled.

What is directory-based edit freeze and when do I need it?

Directory-based edit freeze is a safety mechanism that blocks all file modifications outside a specified path. You need it during safety-critical maintenance workflows or debugging live systems where edits must be strictly contained.

Does guard mode work with existing gstack hooks?

Yes, full safety mode integrates directly with existing gstack hooks. It relies on the careful and freeze components to enforce safety checks before tool use, ensuring seamless operation within your established workflows.

What's the best way to lock down a production environment for maximum safety?

The best way to lock down a production environment is to invoke a full safety mode that combines destructive command warnings with directory-scoped edit restrictions. This provides maximum safety when touching prod or debugging live systems.