菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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-module |
| description | 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. |
Create a new module file in the CLI's modules directory.
~/.<cli>/modules/ (default) — if the CLI was generated to a custom path, ask the user<module>.sh following the conventions belowoosh lint <cli> <module> to validate the new moduleRead references/annotations.md in this skill directory for the full annotation reference and module template.
Key rules:
#!/bin/bash and #@module <Name> - <description>. ${MODULES_DIR}/../oo.shUPPER_SNAKE_CASE, prefixed with module name (e.g., DEPLOY_ENV in deploy.sh)main $0 "$@"sed, awk, grep in hot paths — bash builtins only