Generate the `bash run.sh --files=''` command for a script in software/scripts/. Use when you want to test-run a specific script.
Generate the matching bash run.sh --files='...' command for a script in software/scripts/.
The user's query is: $ARGUMENTS
run.sh --files=. Per CLAUDE.md, these are files in software/scripts/ with .js or .sh extensions._ prefix (_init.js, _only.js, _only.sh, _full-setup.sh, _full-setup.ps1.bash)~ prefix (~cleanup.js, ~wrapup.sh)software/bootstrap/software/tools/software/tests/software/metadata/.common.js suffixed files (e.g. editor.common.js)bash-autocomplete-complete-spec-skeleton.bash.jsonc, .zip, .ini, .gitconfig, .bash, .ps1)software/scripts/mac/brew.sh -> --files="mac/brew.sh").find software/scripts -type f \( -name '*.js' -o -name '*.sh' \) to get all candidate scripts.$ARGUMENTS by spaces/commas into individual queries. Fuzzy-match each query against the remaining filenames (basename without extension, or partial path match).--files= value and execute: bash run.sh --files="fzf.js,git.js,mac/brew.sh"The --files= value should use paths relative to software/scripts/ (e.g. fzf.js, mac/brew.sh, git.js), comma-separated for multiple scripts.
Always run the command after resolving all matches -- don't just print it.