rb:verify

Verify Ruby Work

Run verification in priority order, stopping at the first failure. Each step must pass before proceeding to the next.

Iron Laws

1. Never commit with failing tests.
2. Never skip security scans on public-facing code.
3. Always verify autoloading after structural changes.
4. Never ignore Zeitwerk check failures.

Tool Selection Policy

• Read ${REPO_ROOT}/.claude/.runtime_env when present and non-symlinked; use its tool booleans as the primary command-selection source of truth.
• Prefer direct tools as the source of truth:
  • bundle exec standardrb or bundle exec rubocop
  • bundle exec brakeman
• Use lefthook run <hook> only when cached runtime detection shows:
  • LEFTHOOK_AVAILABLE=true
  • LEFTHOOK_CONFIG_PRESENT=true
  • LEFTHOOK_LINT_SECURITY_COVERED=true
• If Lefthook is available but no config is detected, ask the user where the config lives before treating it as authoritative.
• LEFTHOOK_DIFF_LINT_COVERED=true means Lefthook covers diff-scoped Pronto/RuboCop review only; it does not replace full direct linting.
• Tests are separate from Lefthook policy and should stay targeted/full based on change scope.
• Treat pronto as an optional final diff-scoped pass:
  • run it after direct lint/security checks
  • do not use it as a substitute for StandardRB/RuboCop or Brakeman

When cached runtime state is available:

• STANDARDRB_AVAILABLE=true → prefer bundle exec standardrb
• else RUBOCOP_AVAILABLE=true → prefer bundle exec rubocop
• BRAKEMAN_AVAILABLE=true → run bundle exec brakeman
• PRONTO_AVAILABLE=true → allow optional final bundle exec pronto run -c MERGE_BASE_VALUE
• VERIFY_COMPOSITE_AVAILABLE=true → treat that as a hint that a repo-native composite verifier may exist, then re-detect it from the working tree before running it
• LEFTHOOK_* booleans control whether Lefthook is an acceptable wrapper, not whether direct checks disappear

Project-Native Composite Runners