plugins/bash-development/skills/bash-53-features/SKILL.md
Bash 5.3 release features and improvements with practical examples. Use when working with Bash 5.3 features, new command substitution, GLOBSORT, loadable builtins, or when user asks about Bash 5.3 changes, new features, or version-specific capabilities.
npx skillsauth add jamie-bitflight/claude_skills bash-53-featuresInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Released in July 2025, Bash 5.3 introduces significant enhancements including revolutionary command substitution syntax, new variables, loadable builtins, and improved C standard conformance.
${ command; }Execute commands without forking, dramatically improving performance:
# Traditional command substitution (creates subshell)
result=$(echo "Hello, World")
# NEW: In-shell command substitution (no fork!)
# Note: a space (or tab/newline/|) is required after the opening '{'
result=${ echo "Hello, World"; }
# Practical example: Fast variable assignment
config_value=${ grep "^timeout=" config.txt | cut -d= -f2; }
# Performance comparison function
benchmark_substitution() {
local i
local start end
echo "Testing traditional substitution..."
start="${EPOCHREALTIME}"
for ((i = 0; i < 1000; i++)); do
result=$(echo "${i}")
done
end="${EPOCHREALTIME}"
printf 'Traditional: %.4f seconds\n' \
"$(awk "BEGIN {print ${end} - ${start}}")"
echo "Testing new in-shell substitution..."
start="${EPOCHREALTIME}"
for ((i = 0; i < 1000; i++)); do
result=${ echo "${i}"; }
done
end="${EPOCHREALTIME}"
printf 'In-shell: %.4f seconds\n' \
"$(awk "BEGIN {print ${end} - ${start}}")"
}
benchmark_substitution
Benefits:
${| command; }Execute commands and automatically store output in REPLY. Note: REPLY is local to the
substitution — its value is restored after completion, so capture it immediately:
Code examples
Benefits:
# String manipulation - use in-shell for efficiency
filename="document.txt"
basename=${ echo "${filename%.*}"; }
extension=${ echo "${filename##*.}"; }
# Output capture - use REPLY for clarity
${| df -h / | tail -1 | awk '{print $5}'; }
disk_usage="${REPLY}"
echo "Disk usage: ${disk_usage}"
# Complex pipelines - traditional might still be clearer
result=$(cat file.txt | grep pattern | sort | uniq)
Control the sorting order of filename and pathname expansion. The specifier is optionally
prefixed with + (ascending, default) or - (descending):
Code examples
Available sort specifiers:
name — Alphabetical by filenamesize — By file sizemtime — By modification timeatime — By access timectime — By inode change timeblocks — By allocated block countnumeric — Numeric sort on leading digits in filenamenosort — Disable sorting (glob order)+ (ascending, default) or - (descending)compgen with Variable StorageStore completions directly in a variable:
Code examples
read with Readline Completion (-E)Interactive input with autocompletion:
# Enable readline completion during read
choose_file() {
local file
echo "Enter filename (tab for completion):"
read -e -r -E -p "> " file
if [[ -f "${file}" ]]; then
echo "Selected: ${file}"
return 0
else
echo "File not found: ${file}"
return 1
fi
}
choose_file
# Practical example: Interactive configuration
configure_app() {
local config_file
echo "Select configuration file:"
read -e -r -E -p "Config: " config_file
if [[ -f "${config_file}" ]]; then
${| grep -c "^[^#]" "${config_file}"; }
local line_count="${REPLY}"
echo "Found ${line_count} active configuration lines"
fi
}
source with Path (-p)Specify search path for sourced scripts:
Code examples
printf EnhancementsNew options for multibyte strings and representations:
# Enhanced printf options
printf '%q\n' "string with spaces" # Shell-quoted output
# NEW: Multibyte string support improvements
text="Hello, 世界"
printf 'Length: %d bytes\n' "${#text}"
# Practical example: Safe command construction
build_command() {
local -a args=("$@")
local arg cmd=""
for arg in "${args[@]}"; do
cmd+=$(printf '%q ' "${arg}")
done
echo "Safe command: ${cmd}"
}
build_command ls "-l" "file with spaces.txt"
kv - Key-Value ArraysCreate associative arrays from key-value data. Note: The kv builtin existence is
confirmed in Bash 5.3; the exact interface shown below is illustrative — verify with
help kv after loading:
Code examples
strptime - Date ParsingParse textual dates into Unix timestamps. Note: The strptime builtin existence is
confirmed in Bash 5.3; the exact interface shown below is illustrative — verify with
help strptime after loading:
Code examples
fltexpr - Floating-Point CalculationsPerform floating-point arithmetic without external tools:
Code examples
Enhanced POSIX compliance:
# Enable POSIX mode
set -o posix
# String comparisons now follow locale rules
[[ "ä" < "z" ]] # Locale-dependent comparison
# Improved POSIX conformance in builtins
# test, trap, wait, bind all more strictly conformant
# Practical example: Portable script header
#!/usr/bin/env bash
if [[ "${BASH_VERSINFO[0]}" -ge 5 ]] && [[ "${BASH_VERSINFO[1]}" -ge 3 ]]; then
# Bash 5.3+ available, use modern features
USE_MODERN_FEATURES=1
else
# Fall back to POSIX mode for portability
set -o posix
USE_MODERN_FEATURES=0
fi
More detailed error messages:
Code examples
Bash 5.3 improves conformance to modern C standards (the build minimum remains C90):
Note: This primarily affects developers compiling Bash from source, not end users.
${ cmd; }) dramatically reduces overheadGLOBSORT# Benchmark: Traditional vs new substitution
benchmark() {
local iterations=10000
local i start end
start="${EPOCHREALTIME}"
for ((i = 0; i < iterations; i++)); do
result=$(echo test)
done
end="${EPOCHREALTIME}"
printf 'Traditional: %.4f seconds\n' \
"$(awk "BEGIN {print ${end} - ${start}}")"
start="${EPOCHREALTIME}"
for ((i = 0; i < iterations; i++)); do
result=${ echo test; }
done
end="${EPOCHREALTIME}"
printf 'In-shell: %.4f seconds\n' \
"$(awk "BEGIN {print ${end} - ${start}}")"
}
benchmark
Most scripts compatible, but consider:
# Take advantage of new command substitution for performance
# OLD:
for file in *; do
size=$(stat -f%z "${file}" 2>/dev/null)
done
# NEW (faster):
for file in *; do
${| stat -f%z "${file}" 2>/dev/null; }
size="${REPLY}"
done
# Use GLOBSORT for better file processing
GLOBSORT="-mtime"
for file in *.log; do
process_recent_log "${file}"
done
# Leverage new builtins where appropriate
# Instead of: awk calculation
# Use: fltexpr for floating-point math
# Check for Bash 5.3 features
if [[ "${BASH_VERSINFO[0]}" -ge 5 ]] && [[ "${BASH_VERSINFO[1]}" -ge 3 ]]; then
echo "Bash 5.3+ features available"
CAN_USE_INSITU_SUBSTITUTION=1
CAN_USE_GLOBSORT=1
else
echo "Bash version: ${BASH_VERSION}"
CAN_USE_INSITU_SUBSTITUTION=0
CAN_USE_GLOBSORT=0
fi
For broader Bash development patterns and best practices, see:
development
When an application needs to store config, data, cache, or state files. When designing where user-specific files should live. When code writes to ~/.appname or hardcoded home paths. When implementing cross-platform file storage with platformdirs.
testing
Enforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Use this skill when about to execute implementation actions (Bash, Write, Edit) to verify hypothesis-action alignment. Blocks execution when hypothesis unverified or action targets different system than hypothesis identified. Critical for preventing cognitive dissonance where correct diagnosis leads to wrong implementation.
tools
Reference guide for the Twelve-Factor App methodology — 15 principles (12 original + 3 modern extensions) for building portable, resilient, cloud-native applications. Use when evaluating application architecture, designing cloud-native services, reviewing codebases for methodology compliance, advising on configuration, scaling, observability, security, and deployment patterns. Incorporates the 2025 open-source community evolution and cloud-native reinterpretations of each factor.
tools
Converts user-facing documentation (how-to guides, tutorials, API references, examples) in any format — Markdown, PDF, DOCX, PPTX, XLSX, AsciiDoc, RST, HTML, Jupyter notebooks, man pages, TOML/YAML/JSON configs, and plain text — into Claude Code skill directories with SKILL.md plus thematically grouped references/*.md files. Use when given a docs directory or mixed-format documentation to transform into an AI skill. Uses MCP file-reader server for binary formats.