Jamie-BitFlight/bash-lint

Esta habilidade deve ser usada quando o usuário pedir para "lintar script bash", "executar shellcheck", "formatar script shell", "usar shfmt", "corrigir erros do shellcheck", ou mencionar linting, formatação, qualidade de código ou hooks pre-commit para bash.

O que é bash-lint?

O skill **Jamie-BitFlight/bash-lint** fornece integração completa com ShellCheck e shfmt para garantir a qualidade de scripts Bash. O ShellCheck é uma ferramenta de linting que analisa scripts shell e aponta problemas comuns, como variáveis não entre aspas (SC2086), substituição de comandos não citada (SC2046) e declarações que mascaram códigos de saída (SC2155). Já o shfmt formata automaticamente scripts shell, aplicando indentação, espaçamento e quebras de linha consistentes. O skill também cobre a integração com hooks pre-commit para executar essas ferramentas automaticamente antes de commits, e com pipelines de CI/CD (GitHub Actions e GitLab CI) para garantir que todos os scripts sigam os mesmos padrões. Inclui diretivas inline para suprimir avisos específicos, configuração via .editorconfig e integração com editores como VS Code e Vim. Ideal para desenvolvedores que desejam manter uma base de código shell limpa, segura e padronizada.

Funciona com~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 Programação e Desenvolvimento skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Linting Bash

Integração Shellcheck e shfmt para garantia de qualidade de scripts bash.

Shellcheck

Instalação

# Debian/Ubuntu
apt install shellcheck

# macOS
brew install shellcheck

# A partir do código fonte
cabal update && cabal install ShellCheck

Uso Básico

# Verificar arquivo único
shellcheck script.sh

# Verificar vários arquivos
shellcheck *.sh

# Com dialeto shell específico
shellcheck --shell=bash script.sh
shellcheck --shell=sh script.sh

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

# Formatos de saída
shellcheck --format=gcc script.sh    # Estilo GCC
shellcheck --format=json script.sh   # JSON para ferramentas
shellcheck --format=diff script.sh   # Diff unificado

Códigos Comuns do Shellcheck

CódigoProblemaCorreção
SC2086Aspas duplas para evitar globbing/divisão"$var"
SC2046Cite a substituição de comando"$(cmd)"
SC2006Use $() em vez de crases$(cmd)
SC2034Variável parece não utilizadaRemova ou exporte
SC2155Declare e atribua separadamenteSepare local var; var=$(...)
SC2164Use cd ... || exitTrate falha do cd
SC2181Verifique status de saída diretamenteif cmd; then
SC2129Considere agrupar escritasUse { } > arquivo
SC1090Não foi possível seguir arquivo sourceadoUse # shellcheck source=caminho
SC2154Variável referenciada mas não atribuídaInicialize ou declare

Diretivas do Shellcheck

# Desabilitar para a próxima linha
# shellcheck disable=SC2086
echo $var_nao_entre_aspas

# Desabilitar para o arquivo inteiro (no topo)
# shellcheck disable=SC2086,SC2046

# Especificar arquivo de origem para source
# shellcheck source=./lib/functions.sh
source "$SCRIPT_DIR/lib/functions.sh"

# Especificar dialeto shell
# shellcheck shell=bash

# Desabilitar para bloco (não suportado - use por linha)

Padrões de Diretivas Inline

# Desabilitar aviso específico com explicação
# shellcheck disable=SC2034 # Variável usada pelo script que faz source
readonly CONFIG_VERSION="1.0"

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

# Diretiva de source para caminhos dinâmicos
# shellcheck source=/dev/null
source "${CAMINHO_DINAMICO}/config.sh"

shfmt

Instalação

# macOS
brew install shfmt

# Instalação Go
go install mvdan.cc/sh/v3/cmd/shfmt@latest

# Snap
snap install shfmt

# Download binário
# De https://github.com/mvdan/sh/releases

Uso Básico

# Formatar e imprimir na saída padrão
shfmt script.sh

# Formatar no local
shfmt -w script.sh

# Verificar formatação (código de saída 1 se não formatado)
shfmt -d script.sh

# Diretório recursivo
shfmt -w .
shfmt -w scripts/

Opções de Formatação

# Indentação
shfmt -i 2 script.sh  # Indentação de 2 espaços
shfmt -i 4 script.sh  # Indentação de 4 espaços
shfmt -i 0 script.sh  # tabs (padrão)

# Operadores binários no início da linha
shfmt -bn script.sh

# Casos switch indentados
shfmt -ci script.sh

# Operadores de redirecionamento seguidos por espaço
shfmt -sr script.sh

# Manter alinhamento de colunas
shfmt -kp script.sh

# Chave de abertura da função em linha separada
shfmt -fn script.sh

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

Configuração (.editorconfig)

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

Exemplos de Transformação

Antes do shfmt:

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

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

Depois de shfmt -i 4 -ci:

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

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

Integração com 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: hooks locais
  - 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"]

Executando Pre-commit

# Instalar hooks
pre-commit install       # ou: prek install

# Executar em todos os arquivos
pre-commit run --all-files       # ou: prek run --all-files

# Executar hook específico
pre-commit run shellcheck --all-files
pre-commit run shfmt --all-files

# Executar em arquivos específicos
pre-commit run --files script.sh

Integração com CI/CD

GitHub Actions

name: Lint Shell

on: [push, pull_request]

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

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

      - name: Verificar formatação com 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 .

Corrigindo Problemas Comuns

SC2086: Aspas para evitar divisão

# Ruim
echo $var

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

SC2155: Declare e atribua separadamente

# Ruim - mascara status de saída
local var=$(algum_comando)

# Bom
local var
var=$(algum_comando)

SC2164: Use cd || exit

# Ruim
cd "$dir"
rm -rf *

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

# Ou com subshell
(cd "$dir" && rm -rf *)

SC2181: Verifique saída diretamente

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

# Bom
if comando; then

SC1090/SC1091: Problemas de source

# Adicione diretiva para source dinâmico
# shellcheck source=/dev/null
source "$CAMINHO_DINAMICO/lib.sh"

# Ou especifique caminho real
# shellcheck source=./lib/functions.sh
source "$SCRIPT_DIR/lib/functions.sh"

Integração com Editores

VS Code

Instale a extensão "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

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

" Com coc.nvim
" Instale a extensão coc-sh

Melhores Práticas

  1. Execute shellcheck cedo - integre no editor e no CI
  2. Corrija problemas, não suprima - desabilite apenas com boa razão
  3. Documente supressões - explique por que a regra está desabilitada
  4. Use níveis de severidade - --severity=warning para CI
  5. Formatação consistente - use shfmt no pre-commit
  6. Versione as ferramentas - fixe versões no 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).

Habilidades Relacionadas