Community코딩 & 개발github.com

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.

bash-51-features란 무엇인가요?

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

지원 대상Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/bash-development/skills/bash-51-features

Installed? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

Bash 5.1 Features and Improvements

Released in December 2020, Bash 5.1 introduced several notable features and improvements for modern shell scripting.

New Shell Variables

EPOCHSECONDS and EPOCHREALTIME

Two new special variables for accessing current time:

# Get current Unix timestamp in seconds
echo "Current timestamp: ${EPOCHSECONDS}"

# Get current Unix timestamp with microsecond precision
echo "High precision timestamp: ${EPOCHREALTIME}"

# Practical example: Simple benchmarking
start="${EPOCHREALTIME}"
# ... some operation ...
sleep 0.5
end="${EPOCHREALTIME}"
duration=$(awk "BEGIN {print ${end} - ${start}}")
echo "Operation took ${duration} seconds"

# Example: Log with precise timestamps
log_message() {
    printf '[%s.%06d] %s\n' \
        "$(date -d "@${EPOCHSECONDS}" '+%Y-%m-%d %H:%M:%S')" \
        "${EPOCHREALTIME#*.}" \
        "$*"
}

log_message "Starting process"

Use cases:

  • Precise performance measurement
  • High-resolution timestamps for logging
  • Avoiding external date command calls
  • Microsecond-precision timing in scripts

SRANDOM Variable

Cryptographically strong random numbers:

# Generate secure random number (if available)
if [[ -n "${SRANDOM}" ]]; then
    secure_random="${SRANDOM}"
    echo "Secure random: ${secure_random}"
else
    echo "SRANDOM not available (requires getrandom/getentropy)"
fi

# Practical example: Generate temporary file with secure random name
temp_file="/tmp/secure_${SRANDOM}_${EPOCHSECONDS}.tmp"

Note: SRANDOM requires system support for getrandom() or getentropy() syscalls.

Improved Redirection Syntax

{varname} Redirection

Assign file descriptor to variable for better file handle management:

# Open file descriptor and store in variable
exec {fd}< input.txt
while IFS= read -r -u "${fd}" line; do
    echo "Read: ${line}"
done
exec {fd}<&-  # Close the file descriptor

# Practical example: Multiple file handles
exec {input_fd}< data.txt
exec {output_fd}> results.txt
exec {error_fd}> errors.txt

process_data() {
    while IFS= read -r -u "${input_fd}" line; do
        if validate_line "${line}"; then
            echo "Processed: ${line}" >&"${output_fd}"
        else
            echo "Error: ${line}" >&"${error_fd}"
        fi
    done
}

process_data
exec {input_fd}<&-
exec {output_fd}>&-
exec {error_fd}>&-

Benefits:

  • Named file descriptors instead of magic numbers
  • Automatic FD allocation avoids conflicts
  • More readable and maintainable code
  • Easier tracking of open file handles

Array Enhancements

Improved Associative Array Handling

Better support for complex array operations:

# Declare associative array with typeset
declare -A config=(
    [host]="localhost"
    [port]="8080"
    [debug]="true"
)

# Enhanced array expansion
for key in "${!config[@]}"; do
    printf '%s=%s\n' "${key}" "${config[${key}]}"
done

# Practical example: Configuration parser
parse_config() {
    declare -gA app_config
    local line key value

    while IFS='=' read -r key value; do
        [[ "${key}" =~ ^[[:space:]]*# ]] && continue  # Skip comments
        [[ -z "${key}" ]] && continue                  # Skip empty lines

        # Trim whitespace
        key="${key#"${key%%[![:space:]]*}"}"
        key="${key%"${key##*[![:space:]]}"}"
        value="${value#"${value%%[![:space:]]*}"}"
        value="${value%"${value##*[![:space:]]}"}"

        app_config["${key}"]="${value}"
    done < config.ini
}

Multidimensional Array Support

Improved handling of nested array structures.

Code examples

Readline 8.1 Integration

Enhanced text editing and command-line interaction:

Key Bindings and History

# Configure readline in ~/.inputrc
# Enable case-insensitive completion
set completion-ignore-case on

# Enable visible stats for completions
set visible-stats on

# Show all completions immediately
set show-all-if-ambiguous on

# Use colors for completion matching
set colored-completion-prefix on

Improved History Search

# In your script or .bashrc
# Bind Ctrl+R for reverse incremental search (default, but enhanced in 5.1)
bind '"\C-r": reverse-search-history'

# Bind Ctrl+S for forward incremental search
bind '"\C-s": forward-search-history'

# Improved history handling
shopt -s histappend           # Append to history
shopt -s cmdhist              # Multi-line commands as one entry
HISTCONTROL=ignoreboth        # Ignore duplicates and leading spaces
HISTSIZE=10000
HISTFILESIZE=20000

Signal Handling Improvements

Better signal propagation in subshells and process substitutions:

# Enhanced trap handling in subshells
cleanup() {
    echo "Cleaning up..." >&2
    rm -f "${temp_file}"
    exit 130  # 128 + SIGINT
}

trap cleanup SIGINT SIGTERM

temp_file=$(mktemp)

# Signal properly propagates through pipelines
long_running_task | process_output &
pid=$!

# Wait for background job with proper signal handling
wait "${pid}" 2>/dev/null
exit_code=$?

if [[ ${exit_code} -gt 128 ]]; then
    signal=$((exit_code - 128))
    echo "Process terminated by signal ${signal}" >&2
fi

Bug Fixes and Edge Cases

Subshell Handling

Improved behavior when spawning subshells:

# More reliable subshell variable inheritance
outer_var="parent"

(
    # Subshell now more reliably inherits parent variables
    echo "In subshell: ${outer_var}"
    inner_var="child"
)

# outer_var still accessible, inner_var is not
echo "After subshell: ${outer_var}"

Pattern Matching Edge Cases

Fixed edge cases in glob pattern matching:

# More reliable glob matching with special characters
shopt -s nullglob  # Empty expansion for non-matching globs
shopt -s extglob   # Extended pattern matching

# Example: Match files but handle no matches gracefully
files=(*.txt)
if [[ ${#files[@]} -eq 0 ]]; then
    echo "No .txt files found"
else
    printf 'Found: %s\n' "${files[@]}"
fi

Performance Improvements

  • Faster variable expansion in loops
  • Optimized array operations
  • Reduced memory usage for large arrays
  • Improved efficiency in pattern matching

Compatibility Notes

Upgrading from Bash 5.0

Most scripts are compatible, but note:

  • EPOCHSECONDS and EPOCHREALTIME are new - check for existence if targeting older versions
  • SRANDOM may not be available on all systems
  • Some obscure edge cases in expansion behavior were fixed

Version Check

# Check Bash version before using 5.1 features
if [[ "${BASH_VERSINFO[0]}" -ge 5 ]] && [[ "${BASH_VERSINFO[1]}" -ge 1 ]]; then
    # Safe to use Bash 5.1 features
    timestamp="${EPOCHSECONDS}"
else
    # Fallback for older versions
    timestamp=$(date +%s)
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-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-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.

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

관련 스킬