CommunityProgramación y desarrollogithub.com

Jamie-BitFlight/bash-lint

Esta habilidad debe usarse cuando el usuario solicite "lint de script bash", "ejecutar shellcheck", "formatear script shell", "usar shfmt", "corregir errores de shellcheck" o mencione linting, formateo, calidad de código o ganchos pre-commit para scripts bash/shell.

¿Qué es bash-lint?

Esta habilidad proporciona integración completa de Shellcheck y shfmt para garantizar la calidad del código en scripts Bash. Es útil para desarrolladores y equipos que desean mantener un código shell limpio, seguro y consistente, ya sea localmente, en pipelines CI/CD o mediante ganchos pre-commit. Soporta plataformas como GitHub Actions, GitLab CI y editores como VS Code, Vim y Neovim. El skill detalla instalación, uso básico, opciones de formato, códigos de error comunes con sus soluciones, y patrones de directivas inline para deshabilitar advertencias específicas de Shellcheck.

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

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

Linting de Bash

Integración de Shellcheck y shfmt para garantizar la calidad de scripts bash.

Shellcheck

Instalación

# Debian/Ubuntu
apt install shellcheck

# macOS
brew install shellcheck

# Desde fuente
cabal update && cabal install ShellCheck

Uso básico

# Verificar un solo archivo
shellcheck script.sh

# Verificar múltiples archivos
shellcheck *.sh

# Con dialecto de shell específico
shellcheck --shell=bash script.sh
shellcheck --shell=sh script.sh

# Excluir reglas específicas
shellcheck --exclude=SC2086 script.sh
shellcheck --exclude=SC2086,SC2046 script.sh

# Formatos de salida
shellcheck --format=gcc script.sh    # Estilo GCC
shellcheck --format=json script.sh   # JSON para herramientas
shellcheck --format=diff script.sh   # Diff unificado

Códigos comunes de Shellcheck

CódigoProblemaSolución
SC2086Usar comillas dobles para evitar división"$var"
SC2046Poner entre comillas la sustitución de comando"$(cmd)"
SC2006Usar $() en lugar de acentos graves$(cmd)
SC2034Variable parece no usarseEliminar o exportar
SC2155Declarar y asignar por separadoSeparar local var; var=$(...)
SC2164Usar `cd ...
SC2181Verificar estado de salida directamenteif cmd; then
SC2129Considerar agrupar escriturasUsar { } > archivo
SC1090No se puede seguir archivo fuenteUsar # shellcheck source=ruta
SC2154Variable referenciada pero no asignadaInicializar o declarar

Directivas de Shellcheck

# Deshabilitar para la siguiente línea
# shellcheck disable=SC2086
echo $var_sin_comillas

# Deshabilitar para todo el archivo (al inicio)
# shellcheck disable=SC2086,SC2046

# Especificar archivo fuente para sourcing
# shellcheck source=./lib/functions.sh
source "$SCRIPT_DIR/lib/functions.sh"

# Especificar dialecto de shell
# shellcheck shell=bash

# Deshabilitar para bloque (no soportado - usar por línea)

Patrones de directivas inline

# Deshabilitar advertencia específica con explicación
# shellcheck disable=SC2034 # Variable usada por script source
readonly CONFIG_VERSION="1.0"

# Deshabilitar múltiples códigos
# shellcheck disable=SC2086,SC2046
resultado=$(echo $var)

# Directiva source para rutas dinámicas
# shellcheck source=/dev/null
source "${RUTA_DINAMICA}/config.sh"

shfmt

Instalación

# macOS
brew install shfmt

# Instalación con Go
go install mvdan.cc/sh/v3/cmd/shfmt@latest

# Snap
snap install shfmt

# Descarga binaria
# Desde https://github.com/mvdan/sh/releases

Uso básico

# Formatear y mostrar en stdout
shfmt script.sh

# Formatear en el lugar
shfmt -w script.sh

# Verificar formato (código de salida 1 si no está formateado)
shfmt -d script.sh

# Directorio recursivo
shfmt -w .
shfmt -w scripts/

Opciones de formato

# Indentación
shfmt -i 2 script.sh  # Indentación de 2 espacios
shfmt -i 4 script.sh  # Indentación de 4 espacios
shfmt -i 0 script.sh  # Tabuladores (por defecto)

# Operadores binarios al inicio de línea
shfmt -bn script.sh

# Casos switch indentados
shfmt -ci script.sh

# Operadores de redirección seguidos de espacio
shfmt -sr script.sh

# Mantener alineación de columnas
shfmt -kp script.sh

# Llave de apertura de función en línea separada
shfmt -fn script.sh

# Combinado
shfmt -i 4 -ci -bn script.sh

Configuración (.editorconfig)

# .editorconfig
[*.sh]
indent_style = space
indent_size = 4
shell_variant = bash
binary_next_line = true
switch_case_indent = true
space_redirects = true

Ejemplos de transformación

Antes de shfmt:

if [ -f "$archivo" ];then
echo "existe"
fi

for i in 1 2 3;do
    procesar $i
done

Después de shfmt -i 4 -ci:

if [ -f "$archivo" ]; then
    echo "existe"
fi

for i in 1 2 3; do
    procesar $i
done

Integración con Pre-commit

.pre-commit-config.yaml

repos:
  - repo: https://github.com/koalaman/shellcheck-precommit
    rev: v0.9.0
    hooks:
      - id: shellcheck
        args: ["--severity=warning"]

  - repo: https://github.com/scop/pre-commit-shfmt
    rev: v3.7.0-1
    hooks:
      - id: shfmt
        args: ["-i", "4", "-ci", "-w"]

  # Alternativa: ganchos locales
  - repo: local
    hooks:
      - id: shellcheck
        name: shellcheck
        entry: shellcheck
        language: system
        types: [shell]
        args: ["--severity=warning", "-x"]

      - id: shfmt
        name: shfmt
        entry: shfmt
        language: system
        types: [shell]
        args: ["-i", "4", "-ci", "-w"]

Ejecutar Pre-commit

# Instalar ganchos
pre-commit install       # o: prek install

# Ejecutar en todos los archivos
pre-commit run --all-files       # o: prek run --all-files

# Ejecutar gancho específico
pre-commit run shellcheck --all-files
pre-commit run shfmt --all-files

# Ejecutar en archivos específicos
pre-commit run --files script.sh

Integración con CI/CD

GitHub Actions

name: Lint Shell

on: [push, pull_request]

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Ejecutar ShellCheck
        uses: ludeeus/action-shellcheck@master
        with:
          severity: warning

      - name: Verificar formato con shfmt
        uses: mvdan/github-action-shfmt@master
        with:
          flags: -d -i 4 -ci

GitLab CI

shellcheck:
  image: koalaman/shellcheck-alpine:stable
  script:
    - find . -name "*.sh" -exec shellcheck {} +

shfmt:
  image: mvdan/shfmt:latest
  script:
    - shfmt -d -i 4 -ci .

Solución de problemas comunes

SC2086: Usar comillas para evitar división

# Malo
echo $var

# Bueno
echo "$var"
printf '%s\n' "$var"

SC2155: Declarar y asignar por separado

# Malo - oculta el estado de salida
local var=$(comando)

# Bueno
local var
var=$(comando)

SC2164: Usar cd || exit

# Malo
cd "$dir"
rm -rf *

# Bueno
cd "$dir" || exit 1
rm -rf *

# O con subshell
(cd "$dir" && rm -rf *)

SC2181: Verificar salida directamente

# Malo
comando
if [ $? -eq 0 ]; then

# Bueno
if comando; then

SC1090/SC1091: Problemas de source

# Agregar directiva para source dinámico
# shellcheck source=/dev/null
source "$RUTA_DINAMICA/lib.sh"

# O especificar ruta real
# shellcheck source=./lib/functions.sh
source "$SCRIPT_DIR/lib/functions.sh"

Integración con editores

VS Code

Instalar la extensión "ShellCheck" de Timon Wong.

// settings.json
{
    "shellcheck.enable": true,
    "shellcheck.run": "onSave",
    "shellcheck.executablePath": "shellcheck",
    "editor.formatOnSave": true,
    "[shellscript]": {
        "editor.defaultFormatter": "foxundermoon.shell-format"
    }
}

Vim/Neovim

" Con ALE
let g:ale_linters = {'sh': ['shellcheck']}
let g:ale_fixers = {'sh': ['shfmt']}
let g:ale_sh_shfmt_options = '-i 4 -ci'

" Con coc.nvim
" Instalar extensión coc-sh

Buenas prácticas

  1. Ejecutar shellcheck temprano - integrar en editor y CI
  2. Corregir problemas, no suprimirlos - solo deshabilitar con buena razón
  3. Documentar supresiones - explicar por qué se deshabilita la regla
  4. Usar niveles de severidad - --severity=warning para CI
  5. Formateo consistente - usar shfmt en pre-commit
  6. Versiones fijas de herramientas - fijar versiones en CI/pre-commit

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