2
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill 89jobrien/steve --skill command-optimization- SKILL.md5.8 KB
Overview
This skill helps design, build, and optimize command-line interfaces with a focus on practical developer ergonomics. It covers command design patterns, argument parsing, task automation, error handling, and clear command documentation. Use it to create consistent, user-friendly CLI commands and improve existing tooling.
How this skill works
I analyze command goals and target workflows, then propose action-oriented names, argument schemas, and sensible defaults. I recommend parsing strategies (positional vs options), validation checks, and helpful help text. I also provide error-handling patterns, dry-run/verbose modes, and examples for implementation in Python or shell-based tooling.
When to use it
- Creating new CLI commands or utilities
- Designing argument and option structures
- Optimizing an existing command's UX and feedback
- Automating repetitive tasks with scripts
- Implementing robust input validation and errors
Best practices
- Use clear, action-oriented command names and consistent patterns
- Prefer sensible defaults and progressive disclosure in help text
- Validate inputs early and provide actionable error messages
- Support --dry-run and --verbose for safe testing and debugging
- Require confirmation for destructive actions and provide rollback options
Example use cases
- Generate a component scaffolder command with path, type, and test flags
- Design a db:migrate tool with create, rollback, status, and target options
- Create an analysis command that accepts glob patterns and outputs reports
- Convert repetitive local tasks into idempotent CLI commands with --dry-run
- Improve an existing lint command to accept files, directories, and globs with clear errors
FAQ
Use positional arguments for the primary target (e.g., resource name) and options for modifiers; document required positions clearly in help text.
How do I present advanced options without overwhelming users?
Use progressive disclosure: show common flags in the default help and add an --advanced or --help-verbose section for edge options.