security-reminder-hook-blocks-literal-exec-eval-in-prose

The security_reminder_hook regex triggers on literal exec( and eval( tokens even in documentation, comments, or handoff files — not just executable code. This caused two false-positive blocks during Phase 2: once when writing the security-auditor skill and once when committing the handoff doc that described the hook itself. Fix by rephrasing to descriptive language (e.g., ‘execute call’ instead of exec() whenever writing prose that references these patterns.

Related

• spec-reviewer-blocks-on-os-system-in-test-code
• destructive-hook-regex-matches-rm-inside-echo-strings
• docker
• 2026-04-04-oracle-001-self-architecture-analysis
• capability-wiring-gap-documentation-is-not-activation
• security-hook-blocks-exec-eval-tokens-in-prose
• security-hook-blocks-literal-exec-eval-tokens-in-prose
• security-hook-blocks-literal-exec-eval-in-prose
• security-hook-fires-on-literal-exec-eval-tokens-in-prose
• security-hook-triggers-on-literal-exec-eval-tokens-in-prose