Prefer long flags in the bash skill
Assisted-by: Claude Opus 4.8 via Claude Code
change pxpwwqokuovplxxtxxolloprrssvwmvr
commit 50400d89fc34501e7642859145acda796c292e65
author Alpha Chen <alpha@kejadlen.dev>
date
parent zzyqrxly
diff --git a/ai/skills/bash/SKILL.md b/ai/skills/bash/SKILL.md
index fa0806fe..c13cd2f8 100644
--- a/ai/skills/bash/SKILL.md
+++ b/ai/skills/bash/SKILL.md
@@ -31,6 +31,17 @@ Wrapping logic in `main()` and calling `main "$@"` at the bottom
 prevents partial execution if the script is truncated during
 download or write.
 
+## Command flags
+
+Prefer long flags over short ones in scripts. `grep --invert-match
+--line-number` reads more clearly than `grep -vn`, and a reviewer
+doesn't have to recall what each letter means. Short flags optimize
+for interactive typing; scripts are read far more often than they're
+written, so favor legibility.
+
+Use short flags only when no long form exists, or when long flags
+would harm clarity (for example, repeated `-v` to raise verbosity).
+
 ## Executable permissions
 
 Scripts meant to be run directly need the executable bit (`chmod +x`).