[KuSh]

What

Filter functions repeated their own module name, so every cross-module call read as mypy_cmd::filter_mypy_output. The module path already supplies the tool name.

This is not a new convention: .claude/rules/rust-patterns.md has prescribed plain filter_output in its "Module Structure" section all along (lines 231-232). The code had drifted from its own documented house style; this aligns them.

module	before	after
bun_cmd	filter_bun_pkg	filter_pkg
	filter_bun_pm_ls_json	filter_pm_ls_json
	filter_bun_pm_ls_text	filter_pm_ls_text
	filter_bun_pm_ls	filter_pm_ls
	filter_bun_pm_ls_tree	filter_pm_ls_tree
deno_cmd	filter_deno_output	filter_output
prettier_cmd	filter_prettier_output	filter_output
artisan_cmd	filter_artisan_output	filter_output
	filter_artisan_test_output	filter_test_output
mypy_cmd	filter_mypy_output	filter_output
ruff_cmd	filter_ruff_check_json	filter_check_json
	filter_ruff_format	filter_format
sqlfluff_cmd	filter_sqlfluff_lint_json	filter_lint_json
json_cmd	filter_json_compact	filter_compact
	filter_json_string	filter_schema

Reads better where it matters most — the pipe_cmd registry:

"ruff-check"    => Some(crate::cmds::python::ruff_cmd::filter_check_json),
"sqlfluff-lint" => Some(crate::cmds::python::sqlfluff_cmd::filter_lint_json),

Not a behaviour change

Pure rename. The user-facing rtk pipe -f filter names ("mypy", "ruff-check", "sqlfluff-lint", …) are unchanged, so no CLI surface moves. cargo fmt --all --check, cargo clippy --all-targets and cargo test --all all pass.

Two judgement calls

• bun_cmd::run_bunx left alone. bunx is a distinct tool from bun, so that is not stutter. Flagging it because a regex-driven pass would have renamed it.
• json_cmd::filter_json_string → filter_schema is a semantic fix, not just destuttering. It returns a schema representation (types only, no values), so the old name described its input rather than its output. Easy to drop from this PR if you'd rather keep the change purely mechanical.

Doc drift

src/cmds/README.md taught the stuttering pattern in both its worked example and its "Adding a New Command Filter" checklist, which would have pulled the convention straight back on the next filter. Both are updated, and the naming rule is now stated explicitly rather than left implicit.

🤖 Generated with Claude Code