CommunityProgramación y desarrollogithub.com

Jamie-BitFlight/bash-development

Esta habilidad debe utilizarse cuando el usuario solicite

¿Qué es bash-development?

Esta habilidad proporciona patrones básicos y mejores prácticas para el desarrollo de scripts Bash 5.1+. Su propósito es guiar a los agentes de IA (como Claude Code, Cursor y Codex) en la escritura de scripts bash modernos y robustos, ofreciendo un marco completo que abarca desde el encabezado esencial del script hasta el manejo de errores, el análisis de argumentos, las operaciones con cadenas y arreglos, y las expresiones condicionales avanzadas. La habilidad es útil porque estandariza el estilo y la calidad del código, promoviendo el uso de características nativas de Bash en lugar de herramientas externas, lo que mejora la portabilidad y el rendimiento. Funciona basándose en su archivo SKILL.md, que incluye ejemplos de código, enlaces a archivos de referencia y pautas de rendimiento, asegurando que el agente genere scripts consistentes, seguros y eficientes.

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

Installed? Explore more Programación y desarrollo skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Desarrollo Bash

Patrones básicos y mejores prácticas para el desarrollo de scripts Bash 5.1+. Proporciona modismos bash modernos, manejo de errores, análisis de argumentos y alternativas bash puras a comandos externos.

Fundamento del Script

Todo script comienza con el encabezado esencial:

#!/usr/bin/env bash
set -euo pipefail

Opciones set explicadas:

  • -e - Salir inmediatamente al fallar un comando
  • -u - Tratar las variables no definidas como errores
  • -o pipefail - La tubería falla si falla cualquier comando

Patrón de Metadatos del Script

SCRIPT_NAME=$(basename "${BASH_SOURCE[0]}")
SCRIPT_DIR=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
readonly SCRIPT_VERSION="1.0.0"
readonly SCRIPT_NAME SCRIPT_DIR

Manejo de Errores

Implementa un manejo de errores basado en trampas para scripts robustos.

Ejemplos de código

Análisis de Argumentos

Plantilla estándar de análisis de argumentos.

Ejemplos de código

Mejores Prácticas para Variables

Usa siempre llaves y entrecomilla las variables:

# Correcto
"${variable}"
"${array[@]}"

# Incorrecto
$variable
${array[*]}  # Usa [@] para iteración correcta

Usa readonly para constantes:

readonly CONFIG_FILE="/etc/app/config"
readonly -a VALID_OPTIONS=("opt1" "opt2" "opt3")

Nota: Nunca uses readonly en scripts incluidos (sourced) - causa errores al volver a cargarlos.

Operaciones con Cadenas (Bash Puro)

Prefiere la expansión nativa de parámetros de bash sobre herramientas externas:

# Recortar espacios en blanco
trimmed="${string#"${string%%[![:space:]]*}"}"
trimmed="${trimmed%"${trimmed##*[![:space:]]}"}"

# Minúsculas/Mayúsculas (Bash 4+)
lower="${string,,}"
upper="${string^^}"

# Extracción de subcadenas
substring="${string:0:10}"      # Primeros 10 caracteres
suffix="${string: -5}"          # Últimos 5 caracteres

# Reemplazar patrones
replaced="${string//old/new}"   # Reemplazar todos
replaced="${string/old/new}"    # Reemplazar el primero

# Eliminar prefijo/sufijo
no_prefix="${string#prefix}"    # Coincidencia más corta
no_prefix="${string##*/}"       # Coincidencia más larga (basename)
no_suffix="${string%suffix}"    # Coincidencia más corta
no_suffix="${string%%/*}"       # Coincidencia más larga

Operaciones con Arreglos

# Declaración
declare -a indexed_array=()
declare -A assoc_array=()

# Iteración segura con nullglob
shopt -s nullglob
for file in *.txt; do
    process "${file}"
done
shopt -u nullglob

# Longitud del arreglo
length="${#array[@]}"

# Añadir elemento
array+=("new_element")

# Iterar con índice
for i in "${!array[@]}"; do
    printf '%d: %s\n' "${i}" "${array[i]}"
done

Operaciones con Archivos

# Leer archivo a una cadena
content="$(<"${file}")"

# Leer archivo a un arreglo (Bash 4+)
mapfile -t lines < "${file}"

# Verificar condiciones de archivos
[[ -f "${file}" ]]    # El archivo regular existe
[[ -d "${dir}" ]]     # El directorio existe
[[ -r "${file}" ]]    # Legible
[[ -w "${file}" ]]    # Escribible
[[ -x "${file}" ]]    # Ejecutable
[[ -s "${file}" ]]    # No vacío

# Creación segura de archivo temporal
temp_file=$(mktemp)
trap 'rm -f "${temp_file}"' EXIT

Expresiones Condicionales

Usa [[ ]] para condicionales (específico de bash, más potente):

# Comparaciones de cadenas
[[ "${var}" == "value" ]]       # Igualdad
[[ "${var}" == pattern* ]]     # Coincidencia de glob
[[ "${var}" =~ ^regex$ ]]      # Coincidencia de expresión regular

# Comparaciones numéricas
(( num > 10 ))                  # Comparación aritmética
[[ "${num}" -gt 10 ]]          # Sintaxis tradicional

# Condiciones compuestas
[[ -f "${file}" && -r "${file}" ]]
[[ "${opt}" == "a" || "${opt}" == "b" ]]

Funciones de Utilidad

Ejemplos de código

Directrices de Rendimiento

  • Usa comandos integrados en lugar de comandos externos cuando sea posible
  • Agrupa operaciones en lugar de bucles para grandes conjuntos de datos
  • Usa printf en lugar de echo por portabilidad y control
  • Evita sub-shells innecesarias en bucles cerrados
  • Usa [[ ]] en lugar de [ ] para comparaciones de cadenas

Recursos Adicionales

Archivos de Referencia

Para patrones y ejemplos detallados:

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-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-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 relacionados