Modern CLI Rules
Modern CLI utilities including fzf, eza, bat, fd, k9s, and other productivity-boosting terminal tools.
3 rules
Standard Exit Code Conventions
Beginner
CLI tools must use proper exit codes — 0 for success, 1 for general errors, 2 for usage errors — to enable reliable scripting, pipelines, and automation.
globs: **/*.sh, **/bin/*, **/cli.*
exit-codes, error-handling, cli-standards, scripting
View Rule
Help Text and Usage Message Standards
Beginner
Every CLI tool must provide --help and --version flags with clear usage messages, argument descriptions, examples, and proper stderr/stdout usage for help output.
globs: **/*.sh, **/bin/*, **/cli.*
help-text, usage, documentation, cli-ux
View Rule
Proper Signal Handling and Cleanup
Intermediate
CLI tools must handle SIGINT, SIGTERM, and other signals gracefully — clean up temporary files, release locks, and exit with appropriate status codes on interruption.
globs: **/*.sh, **/bin/*, **/cli.*
signals, cleanup, trap, temporary-files
View Rule