From no-vibe
Temporarily disables no-vibe write guard for one scoped task (e.g., add .gitignore or fix README typo), executes it exactly, then restores guard if previously active. Invoke via $no-vibe-btw <task>.
How this skill is triggered — by the user, by Claude, or both
Slash command
/no-vibe:no-vibe-btwThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Temporarily disable no-vibe for one scoped task, perform the task, then restore no-vibe if it was previously active.
Temporarily disable no-vibe for one scoped task, perform the task, then restore no-vibe if it was previously active.
Text after $no-vibe-btw is the required task description.
Examples:
$no-vibe-btw add a .gitignore for node$no-vibe-btw scaffold a Makefile with build/test/clean targets$no-vibe-btw fix typo in README.md line 42If task text is missing, stop and tell the user:
$no-vibe-btw requires a task description. Example: $no-vibe-btw add a .gitignore for node.
Run:
was_active=0
[ -f .no-vibe/active ] && was_active=1
Run:
rm -f .no-vibe/active
Verify:
test ! -f .no-vibe/active
If verified, state: temporary btw mode active (.no-vibe/active removed).
Do exactly what the task asks, nothing more.
Scope rules:
Always restore marker if it was active before, even on failure:
if [ "$was_active" = "1" ]; then
mkdir -p .no-vibe && touch .no-vibe/active
fi
Verify:
if [ "$was_active" = "1" ]; then
test -f .no-vibe/active
fi
If verified and was_active=1, state: no-vibe is active again (.no-vibe/active restored).
Give one short summary of files changed and why.
.no-vibe/active when it was previously active..no-vibe/ contents unless task explicitly targets them.$no-vibe off.npx claudepluginhub rizukirr/no-vibe --plugin no-vibeActivates full safety mode with destructive command warnings and directory-scoped edit restrictions. Protects production environments by blocking risky commands and limiting edits to a chosen directory.
Blocks destructive Bash commands like rm -rf, DROP TABLE, git force-push, reset --hard, and restricts file edits to a specific directory. Use for protection on critical systems.
Hard-blocks edits outside declared frozen directories to protect paths during risky changes. Use when you need to prevent accidental writes outside a safe zone.