CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-09-11 07:29:00 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: doc-review fixes — new bins in README table, careful claims precise

Browse Source 
README.md: add gstack-wtree, gstack-evidence, and gstack-issue-guard to the
Standalone binaries table (they shipped in v1.66.1.0 with no user-facing
reference outside CHANGELOG). docs/skills.md: the safety-skills intro said
"no configuration files" which the optional careful-patterns.txt now
contradicts, and the hard-deny description undersold the deny set (the hook
also denies /*, ~/, and $HOME/ forms, not just bare / and ~).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-08-16 09:19:45 -07:00
co-authored by Claude Fable 5
parent 0c160e2a0e
commit 207a94ef0c
2 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/skills.md
+2 -2
View File
@@ -1060,7 +1060,7 @@ Claude: Running independent Codex review...
## Safety & Guardrails
Four skills that add safety rails to any Claude Code session. They work via Claude Code's PreToolUse hooks — transparent, session-scoped, no configuration files.
Four skills that add safety rails to any Claude Code session. They work via Claude Code's PreToolUse hooks — transparent, session-scoped, no configuration required.
### `/careful`
@@ -1076,7 +1076,7 @@ Say "be careful" or run `/careful` when you're working near production, running
Common build artifact cleanups (`rm -rf node_modules`, `dist`, `.next`, `__pycache__`, `build`, `coverage`) are whitelisted — no false alarms on routine operations.
You can override any MEDIUM warning. Two catastrophic shapes are hard-denied instead of asked: recursive deletes of exactly `/`, `~`, or `$HOME`, and force-pushes to the repo's default branch (`--force-with-lease` never triggers the deny; the escape hatch is ending the session-scoped `/careful` session). You can also add your own warn rules — one POSIX ERE per line — in `~/.gstack/careful-patterns.txt` (global) or `~/.gstack/projects/<slug>/careful-patterns.txt` (per-project); custom patterns only ever add warnings, never suppress the built-ins. The guardrails are accident prevention, not access control.
You can override any MEDIUM warning. Two catastrophic shapes are hard-denied instead of asked: recursive deletes of the filesystem root or your home directory (including the `/*`, `~/`, and `$HOME/` forms), and force-pushes to the repo's default branch (`--force-with-lease` never triggers the deny; the escape hatch is ending the session-scoped `/careful` session). You can also add your own warn rules — one POSIX ERE per line — in `~/.gstack/careful-patterns.txt` (global) or `~/.gstack/projects/<slug>/careful-patterns.txt` (per-project); custom patterns only ever add warnings, never suppress the built-ins. The guardrails are accident prevention, not access control.
### `/freeze`