Repository navigation
Support exclude_commands config for auto-rewrite hook #243
Description
Problem
The auto-rewrite hook (rtk-rewrite.sh) rewrites all supported commands unconditionally. There's no way to exclude specific commands from being rewritten without manually editing the hook script — which gets overwritten on the next rtk init -g.
Proposal
Add an exclude_commands option to config.toml that the hook script reads at runtime:
[hooks]
exclude_commands = ["playwright", "curl"]The hook script would check this list before rewriting and skip excluded commands.
Alternative approaches
- Environment variable:
RTK_EXCLUDE="playwright,curl"— simpler but less discoverable - Per-command disable in config:
[commands.playwright] enabled = false - Hook flag:
rtk init -g --exclude playwrightthat generates the hook without those patterns
Any of these would work. The key requirement is that the exclusion survives rtk init -g re-runs.
Activity
fix: curl size guard (#297) + exclude_commands config (#243)
docs: add #297 and #243 to CHANGELOG + exclude_commands in README
fix: curl JSON size guard (#297) + exclude_commands config (#243) (#342)
fix: curl JSON size guard (rtk-ai#297) + exclude_commands config (rtk…
pszymkowiak commentedon Mar 20, 2026
🔍 Automated Triage
featuremediumSummary
Feature request: add exclude_commands config option so specific commands survive rtk init -g re-runs without manual hook edits
📁 Relevant files
config.tomlrtk-rewrite.shTriaged automatically by wshm · This is an automated analysis, not a human review.
nhumrich commentedon Mar 27, 2026
This feature appears to already be in the docs (its in the readme), but doesn't appear to actually work/do anything.
either that, or it doesn't support nested commands like
["git push"]fix: curl JSON size guard (rtk-ai#297) + exclude_commands config (rtk…
pszymkowiak commentedon Jul 7, 2026
exclude_commandswas implemented in #342 (2026-03-05), so this issue looks resolved at a glance — but testing it end-to-end reveals a real gap that undermines the exact example this issue gives.exclude_commands = ["playwright"]does not excludenpx playwright test— only a directplaywright ...invocation.Root cause:
compile_exclude_patterns(registry.rs) turns every entry into an anchored regex^{pattern}($|\s), andis_excludedruns it against the command before wrapper prefixes (npx,pnpm exec,yarn dlx, ...) are stripped. Sincenpx playwright testdoesn't start withplaywright, the pattern never matches.Verified live with the real config file + real Playwright:
And confirmed the practical impact isn't just cosmetic:
rtk playwright --versionactually runs through the dedicatedplaywright_cmdfilter (it happened to fail all its parsing tiers for--versionand fall back to raw output by luck) — fornpx playwright test, the filter would successfully parse and transform the output, exactly what the user configured the exclusion to prevent.Since almost nobody installs Playwright as a global binary —
npx playwright testis the standard invocation — the issue's own headline example doesn't work with the simple syntax it proposes.A workaround exists but isn't documented: writing an explicit anchored regex, e.g.
exclude_commands = ["^(npx )?playwright"], verified working for both forms.Two ways to close the gap:
classify_commandalready does for npx/pnpm exec/yarn dlx/etc.), so a plain["playwright"]entry works regardless of how it's invoked — matching what most users configuring this would expect.fix(hooks): apply exclude_commands to wrapper-invoked forms (rtk-ai#243)
feat(gate): replayable FP corpus — give the gate an empirical stoppin…
fix(gate): guard the backstop's own territory — D2 reviewed, Phase 2 …