bash – Coding skill for AI agents
Language-specific super-code guidelines for bash.
Install the bash skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/bash-ebc74.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /bash – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/bash-ebc74.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $bash – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/bash-ebc74.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /bash – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/bash-ebc74.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /bash – then describe the task you want done.
SKILL.md content
Bash / Shell: Idiomatic Efficiency Reference
Apply only within the requested scope and current project conventions. Preserve behavior, ownership, error handling, accessibility and security; examples are independent fragments, not equivalent rewrites in every context. Verify language/library versions and run relevant checks. Required tests and user-facing progress/results take precedence over brevity rules. Do not install dependencies or delete files merely to follow these examples.
When to Use
- Use this skill when the task matches this description: Language-specific super-code guidelines for bash.
Table of Contents
1. [Quoting & Word Splitting](#quoting)
2. [Conditionals & Tests](#conditionals)
3. [Loops & Iteration](#loops)
4. [Pipes & Process Substitution](#pipes)
5. [Functions & Return Values](#functions)
6. [Error Handling](#errors)
7. [Anti-patterns specific to Bash](#antipatterns)
---
1. Quoting & Word Splitting {#quoting}
# ❌ Unquoted variable (word splitting + globbing)
for f in $files; do rm $f; done
# ✅
for f in "${files[@]}"; do rm -- "$f"; done# ❌ Unquoted command substitution
path=$(find . -name config)
cat $path # breaks on spaces
# ✅
while IFS= read -r -d '' path; do
cat -- "$path"
done < <(find . -name config -type f -print0)# ❌ Using backticks for command substitution
result=`echo hello`
# ✅ — $() nests cleanly
result=$(echo hello)# ❌ String comparison without quotes
if [ $var = "hello" ]; then # breaks if var is empty or has spaces
# ✅
if [[ "$var" = "hello" ]]; thenRule: double-quote every $variable and $(command) unless you specifically need splitting.
---
2. Conditionals & Tests {#conditionals}
# ❌ Single bracket test (POSIX but fragile)
if [ -f "$file" -a -r "$file" ]; then
# ✅ — [[ is safer, supports &&/||, no word splitting inside
if [[ -f "$file" && -r "$file" ]]; then# ❌ Testing command exit status with if [ $? -eq 0 ]
grep -q pattern file
if [ $? -eq 0 ]; then echo "found"; fi
# ✅ — test command directly
if grep -q pattern file; then echo "found"; fi# ❌ String equality with == outside [[
if [ "$a" == "$b" ]; then # == not POSIX in [ ]
# ✅
if [[ "$a" == "$b" ]]; then # Bash
# or POSIX:
if [ "$a" = "$b" ]; then# ❌ Arithmetic with [ ] and string comparison
if [ "$count" -gt 10 ]; then
# ✅ — (( )) for arithmetic
if (( count > 10 )); then---
3. Loops & Iteration {#loops}
# ❌ Parsing ls output
for f in $(ls *.txt); do process "$f"; done
# ✅ — glob directly
for f in *.txt; do
[[ -e "$f" ]] || continue # handle no-match
process "$f"
done# ❌ Reading file line-by-line with for
for line in $(cat file.txt); do # splits on words, not lines
# ✅
while IFS= read -r line || [[ -n "$line" ]]; do
process "$line"
done < file.txt# ❌ Seq for counting
for i in $(seq 1 10); do
# ✅ — brace expansion (Bash)
for i in {1..10}; do
# or C-style:
for (( i = 1; i <= 10; i++ )); do# ❌ Processing command output line-by-line with pipe (subshell trap)
count=0
cat file.txt | while read -r line; do
(( ++count )) # count resets after loop — subshell
done
echo "$count" # always 0
# ✅ — redirect, not pipe
count=0
while IFS= read -r line || [[ -n "$line" ]]; do
(( ++count ))
done < file.txt
echo "$count"---
4. Pipes & Process Substitution {#pipes}
# ❌ Chained grep | grep for AND
grep "error" log.txt | grep "timeout"
# ✅ — single grep with pattern
grep -E "error.*timeout|timeout.*error" log.txt
# or awk for complex logic:
awk '/error/ && /timeout/' log.txt# ❌ cat + pipe (UUOC — Useless Use of Cat)
cat file.txt | grep pattern
# ✅
grep pattern file.txt# ❌ Temp file for diff between commands
cmd1 > /tmp/a.txt
cmd2 > /tmp/b.txt
diff /tmp/a.txt /tmp/b.txt
rm /tmp/a.txt /tmp/b.txt
# ✅ — process substitution
diff <(cmd1) <(cmd2)# ❌ Ignoring pipe failures (only last command's exit code)
false | true
echo $? # 0 — false's failure hidden
# ✅
set -o pipefail
false | true
echo $? # 1---
5. Functions & Return Values {#functions}
# ❌ Using return for string values
get_name() {
return "Alice" # return is for exit codes (0-255)
}
# ✅ — echo + capture
get_name() {
echo "Alice"
}
name=$(get_name)# ❌ Global variables modified inside functions
result=""
compute() { result="done"; }
# ✅ — use local, return via stdout
compute() {
local tmp
tmp=$(do_work)
echo "$tmp"
}
result=$(compute)# ❌ Function keyword (not POSIX)
function my_func {
# ✅
my_func() {---
6. Error Handling {#errors}
# ❌ No error handling — script continues after failure
cd /some/dir
rm -rf * # if cd fails, deletes from wrong directory
# ✅
set -euo pipefail
cd /some/dir || { echo "cd failed" >&2; exit 1; }
# Deletion requires a separately verified target and user scope;
# changing directory and strict mode alone do not make deletion safe.# ❌ No cleanup on exit
tmpfile=$(mktemp)
# ... script might exit early, leaving tmpfile
# ✅ — trap for cleanup
tmpfile=$(mktemp)
trap 'rm -f "$tmpfile"' EXIT# ❌ Silencing errors blindly
command 2>/dev/null
# ✅ — redirect only when you know what you're suppressing
command 2>/dev/null || true # explicit: we expect and accept failureStart every script with set -euo pipefail. Remove selectively where needed.
---
7. Anti-patterns specific to Bash {#antipatterns}
| Anti-pattern | Preferred |
|---|---|
| Parsing ls output | glob: for f in *.txt |
| cat file \| grep | grep pattern file |
| Unquoted $var | "$var" always |
| [ ] for complex tests | [[ ]] |
| Backtick substitution | $(command) |
| $? check after command | if command; then |
| echo for debug | printf '%s\n' (portable) |
| No set -euo pipefail | always set at script top |
| Temp files without cleanup | trap 'rm -f "$tmp"' EXIT |
| eval with user input | avoid; use arrays for dynamic commands |
| #!/bin/sh with Bash features | #!/usr/bin/env bash |
| String math expr 1 + 1 | $(( 1 + 1 )) |
| test -z for number comparison | (( )) for arithmetic |
Limitations
- These are language-specific guidelines and do not cover overall architectural decisions.
- Over-compression might reduce readability; apply judgement.
Related skills
- bats-testing-patterns – Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use…
- hunt-ssti – Hunt server-side template injection (SSTI) across Jinja2 (Flask/Django), Twig (Symfony)…
- bdistill-behavioral-xray – X-ray any AI model's behavioral patterns — refusal boundaries, hallucination tendencies…
- bdistill-knowledge-extraction – Extract structured domain knowledge from AI models in-session or from local open-source…
- before-you-build – Review product risk before coding by checking demand, alternatives, channels, switching…
- behavioral-modes – AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate)…
- experiment-designer – Use when planning product experiments, writing testable hypotheses, estimating sample…
- memento-flashcards – Spaced-repetition flashcards: create, review, quiz, export.