Communitygithub.com

Jamie-BitFlight/bash-53-features

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.

Qu'est-ce que bash-53-features ?

bash-53-features is a Claude Code agent skill that 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.

Compatible avecClaude Code~Codex CLI~Cursor
npx skills add https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/bash-development/skills/bash-53-features

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

Documentation

Bash 5.3 Features and Improvements

Released in July 2025, Bash 5.3 introduces significant enhancements including revolutionary command substitution syntax, new variables, loadable builtins, and improved C standard conformance.

Revolutionary Command Substitution

Efficient In-Shell Execution: ${ 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:

  • No subprocess creation overhead
  • Significantly faster for simple commands
  • Reduced resource usage in loops
  • Same syntax familiarity as command substitution

REPLY Variable Capture: ${| 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:

  • Cleaner code without intermediate variables
  • Consistent capture mechanism
  • Reduced visual clutter
  • Perfect for rapid prototyping

Use Cases Comparison

# 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)

GLOBSORT Variable

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 filename
  • size — By file size
  • mtime — By modification time
  • atime — By access time
  • ctime — By inode change time
  • blocks — By allocated block count
  • numeric — Numeric sort on leading digits in filename
  • nosort — Disable sorting (glob order)
  • Prefix: + (ascending, default) or - (descending)

Enhanced Builtins

compgen with Variable Storage

Store 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 Enhancements

New 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"

New Loadable Builtins

kv - Key-Value Arrays

Create 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 Parsing

Parse 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 Calculations

Perform floating-point arithmetic without external tools:

Code examples

POSIX Mode Improvements

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

Improved Error Reporting

More detailed error messages:

Code examples

C Standard Conformance Improvements

Bash 5.3 improves conformance to modern C standards (the build minimum remains C90):

  • No longer compiles with K&R C compilers
  • Modernized codebase for better conformance
  • Better optimization opportunities
  • Improved type safety

Note: This primarily affects developers compiling Bash from source, not end users.

Performance Improvements

  • Command substitution without forking (${ cmd; }) dramatically reduces overhead
  • Optimized globbing with GLOBSORT
  • Faster builtin operations
  • Reduced memory usage in various operations
# 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

Migration Guide

From Bash 5.2 to 5.3

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

Version Detection

# 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

References

Additional Resources

For broader Bash development patterns and best practices, see:

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

Jamie-BitFlight/agentskill-kaizen-meta-docs

Agentskill kaizen plugin documentation index. Load when needing to read about cross-platform notes, improvement plans, or DuckDB integration.

Jamie-BitFlight/bash-51-features

Bash 5.1 release features and improvements with practical examples. Use when working with Bash 5.1 features, epoch time variables, redirection enhancements, or when user asks about Bash 5.1 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-52-features

Bash 5.2 release features and improvements with practical examples. Use when working with Bash 5.2 features, variable handling enhancements, readline improvements, or when user asks about Bash 5.2 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-development

This skill should be used when the user asks to "write a bash script", "create a shell script", "implement bash function", "parse arguments in bash", "handle errors in bash", or mentions bash development, shell scripting, script templates, or modern bash patterns.

Jamie-BitFlight/bash-lint

This skill should be used when the user asks to "lint bash script", "run shellcheck", "format shell script", "use shfmt", "fix shellcheck errors", or mentions shell script linting, formatting, code quality, or pre-commit hooks for bash.

Jamie-BitFlight/bash-logging

This skill should be used when the user asks to "add logging to bash script", "colorize output", "implement log levels", "CI/CD sections", "terminal colors in bash", or mentions logging functions, emoji output, collapsible CI sections, or shlocksmith.

Jamie-BitFlight/bash-portability

This skill should be used when the user asks about "POSIX compatibility", "portable shell scripts", "cross-shell compatibility", "bashisms", "shebang selection", or mentions writing scripts that work on different shells (bash, sh, dash, zsh) or different systems.

Jamie-BitFlight/bash-testing

This skill should be used when the user asks to "test bash script", "write shell tests", "use shunit2", "use shellspec", "create test suite for bash", or mentions unit testing, test frameworks, mocking, or test-driven development for shell scripts.

Jamie-BitFlight/brainstorming-skill

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using research-validated prompt patterns.

Jamie-BitFlight/clang-format

Configure clang-format code formatting. Use when: user mentions clang-format or .clang-format, analyzing code style/patterns, creating/modifying formatting config, troubleshooting formatting, brace styles/indentation/spacing/alignment/pointer alignment, or codifying conventions.

Jamie-BitFlight/commitlint

When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.

Jamie-BitFlight/conventional-commits

When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.

Jamie-BitFlight/dasel-reference

Use when querying, modifying, or converting JSON, YAML, TOML, XML, CSV, HCL, or INI with dasel v3. Complete reference for selectors, functions, conditionals, variables, spread operator, type casting, and format-specific patterns.

Jamie-BitFlight/data-exploration

Use when exploring unknown structured data files with dasel v3 — discover schema, list keys, find nested values, sample arrays, identify data types across JSON, YAML, TOML, XML, CSV, HCL, INI formats

Jamie-BitFlight/data-transformation

Use when modifying, converting, or transforming structured data with dasel v3 — in-place mutations, format conversion, batch operations, array manipulation, object construction, and merge patterns across JSON, YAML, TOML, XML, CSV, HCL, INI

Jamie-BitFlight/delegate

Decompose substantive work into phases, dispatch each phase to a sub-agent, and adjudicate what comes back. Use whenever a request asks for implementation, investigation, a fix, a review, or any change to files — including small ones — and whenever you are about to read source or run a diagnostic yourself instead of handing it off. Also use when a report from a sub-agent needs judging, when a phase needs re-dispatching, or when a user names one instance of a pattern. Does not apply when your own prompt begins "Your ROLE_TYPE is sub-agent." — then follow references/sub-agent-contract.md instead.

Jamie-BitFlight/enterprise-hibernate-hbm

Dasel v3 query patterns for Hibernate .hbm.xml mapping files — entity-table binding, Java property-to-column extraction, one-to-many set/list/bag relationship tracing, many-to-one foreign key discovery, batch scanning across 60+ HBM files. Use when querying Hibernate ORM class mappings, extracting schema metadata from Java persistence layer, or auditing entity-column relationships in enterprise legacy codebases.

Jamie-BitFlight/enterprise-installanywhere

Dasel v3 query patterns for InstallAnywhere .iap_xml installer definitions — use when querying action sequences, discovering variables, resolving platform conditions, navigating panels, or comparing installer variants. Files are 2.5+ MB, 65,000+ lines — too large for context reads, requires structural dasel queries.

Jamie-BitFlight/enterprise-maven-pom

Dasel v3 selector patterns for Maven POM XML files — use when querying dependency versions, filtering by groupId or scope, extracting module hierarchy from parent POMs, or detecting version conflicts across enterprise multi-module Java projects. Load this skill when working with pom.xml files using dasel.

Jamie-BitFlight/enterprise-spring-xml

Dasel v3 selectors for Spring bean factory XML — use when querying any Spring ApplicationContext XML for bean discovery, dependency wiring, JMS destination mapping, property injection extraction, or cross-bean reference tracing. Load this skill before writing dasel selectors against Spring bean XML files (applicationContext.xml, *_beans.xml, spring-*.xml).

Skills associés