RiccardoGrin Being Careful
Activates session-scoped safety hooks that block dangerous shell commands. Use this when working near production systems, sensitive data, or doing anything where a misfire could cause real damage.
What Gets Blocked
| Pattern | Why | Safe Alternative |
|---|---|---|
rm -rf, rm -f, rm --force |
Irreversible file deletion | trash, targeted rm on specific files |
DROP TABLE, TRUNCATE, bulk DELETE FROM |
Destructive SQL | Review and run manually |
git push --force, git push -f |
Overwrites remote history | git push --force-with-lease |
git reset --hard |
Discards uncommitted work | git stash then reset |
git clean -f |
Deletes untracked files | git stash -u |
git checkout -- . |
Discards all working changes | Stash or commit first |
git branch -D |
Force-deletes branch | git branch -d (safe delete) |
kubectl delete, kubectl --force |
Destroys cluster resources | Review and run manually |
docker system/volume/container prune |
Removes all stopped containers/volumes | Run manually with filters |
How It Works
The skill registers a PreToolUse hook on Bash that inspects each command before execution. If a dangerous pattern is matched, the command is blocked (exit code 2) and Claude sees the reason in stderr. Claude can then suggest a safer alternative.
The hooks are session-scoped — they activate when you invoke /being-careful and last until the session ends.
They do not affect other sessions or persist between sessions.
Gotchas
- The patterns use regex matching, so they may occasionally match in string literals or comments within commands. If a legitimate command is blocked, you can run it manually outside Claude.
git push --force-with-leaseis intentionally allowed — it's the safe alternative to force-push.- The hook does not block
rmwithout-rf/-fflags — targeted file removal is still permitted. - SQL patterns match case-insensitively, so
drop tableandDROP TABLEare both caught.