| name | cli-command-development |
| description | Create or update CLI commands, routes, utilities, and tests in this repo. Use when adding or modifying bin/*, routes/*, utils/*, or related tests. |
| argument-hint | Command or file path + intent (e.g., bin/data-sync.js: add new option) |
| user-invocable | true |
CLI Command Development Skill
Use this skill for CLI-related implementation work across commands, routes, utilities, and tests.
When to Use
- Adding or modifying CLI commands in
bin/
- Updating routes in
routes/
- Modifying shared utilities in
utils/
- Adding or adjusting tests in
tests/
- Updating i18n text and translations
Procedure
- Identify the target file(s) and the command/feature scope.
- Apply the relevant instructions:
- CLI command development rules
- Route development rules (if under
routes/)
- Utility module development rules (if under
utils/)
- i18n translation and text handling rules
- Testing rules and utilities reuse
- Make minimal, testable changes following existing patterns.
- Update i18n properties for any new user-facing text.
- Run targeted tests only if needed.
Notes
- All user-facing text must use text bundles (
bundle.getText).
- Keep CLI command options and validation consistent with existing commands.
- Prefer existing helpers in
utils/ rather than adding new ones.
References