メニュー
Lint oosh CLI annotations for errors and warnings. Use /oosh-lint <cli> [module] to check annotation syntax, flag types, variable naming, and structural issues. Offers --fix for auto-correction. Trigger when the user wants to validate or fix oosh annotations.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create a new module for an oosh CLI. Use /oosh-module <cli> <module> to generate an annotated .sh file in the CLI's modules directory. Trigger when the user wants to add a command, module, or feature to an existing oosh CLI.
Scaffold a new bash CLI using the oosh framework. Use /oosh <name> to generate a complete CLI with entry point, tab completion, modules directory, and sample modules. Trigger when the user wants to create a new bash CLI tool or shell script with flags and completion.
Profile tab-completion performance for an oosh CLI. Use /oosh-trace <cli> [module] to measure shortlist and help timing, flag slow dynamic enum resolvers. Trigger when the user wants to check or optimize oosh completion speed.
| name | oosh-lint |
| description | Lint oosh CLI annotations for errors and warnings. Use /oosh-lint <cli> [module] to check annotation syntax, flag types, variable naming, and structural issues. Offers --fix for auto-correction. Trigger when the user wants to validate or fix oosh annotations. |
Run the annotation linter:
oosh lint <cli> [module]
--fix to auto-correct.#@module, missing main $0 "$@", env var shadows. Explain each and suggest manual fixes.--fix)oosh lint <cli> [module] --fix
Fixes: rename variables to match module prefix, add missing descriptions, escape unquoted strings in defaults. After fixing, re-run lint to confirm clean output.