Repository navigation
v1.8.6
A follow-up to v1.8.5's guardrail-hooks, from its last review round.
How to hold inline code with today's guard: the one-way-door guard doesn't scan python -c or node -e code. To catch it anyway, also list a code rule's pattern under command_rules. It then also asks when a command only names the call, such as a grep for it (Install step 2). The script's own docstring now names what it doesn't see.
Fixed:
- A command after a heredoc's delimiter on the same line (
cat <<'EOF' && gh release delete …) is matched again. test_hooks.pyruns the guard in the session's folder, so a project's owncleanup.pyno longer fails the tests.- A path the guard can't resolve no longer stops it with an error.
Also: retro asks for a hook's canary where it has one, and otherwise reports the wiring unchecked.
What to do: if you installed guardrail-hooks' scripts, copy the new guard_one_way_doors.py and test_hooks.py over your copies, keeping your rules.
Install: README § Install. Lost at any point? Type /product:start-here (Codex: $product:start-here) and say what you have.