Jamie-BitFlight/bash-logging

Este skill deve ser usado quando o usuário pedir para "adicionar logging em script bash", "colorir saída", "implementar níveis de log", "seções CI/CD", "cores de terminal em bash", ou mencionar funções de logging, saída com emojis, seções retráteis de CI, ou shlocksmith.

O que é bash-logging?

Este skill fornece padrões estruturados de logging para scripts bash, incluindo suporte a cores, ícones emoji e integração com ambientes de CI/CD. Ele define funções simples de logging como `print_success`, `print_error`, `print_warning`, `print_info` e `print_debug`, com detecção automática de TTY para habilitar ou desabilitar cores. Além disso, oferece implementações para criar seções retráteis no GitLab CI e agrupamento no GitHub Actions. O skill também inclui a biblioteca de logging shlocksmith, que oferece mais de 20 funções de logging, logging baseado em etapas, suporte a emojis e cores, e gerenciamento de seções de CI. É útil para qualquer desenvolvedor que deseje adicionar logging profissional e legível a scripts bash, especialmente em pipelines de CI/CD.

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

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

Bash Logging

Padrões estruturados de logging para scripts bash com suporte a cores, ícones emoji e integração com CI/CD.

Funções Básicas de Logging

Implementação simples e portável de logging:

# Definições de cores
declare -A colors=(
    [green]=$'\033[0;32m'
    [red]=$'\033[0;31m'
    [yellow]=$'\033[1;33m'
    [blue]=$'\033[0;34m'
    [reset]=$'\033[0m'
)

declare -A emojis=(
    [success]='✅'
    [error]='❌'
    [warning]='⚠️'
    [info]='ℹ️'
    [debug]='🐛'
)

# Funções de logging
print_success() {
    printf '%b %b%b%b\n' "${emojis[success]}" "${colors[green]}" "$*" "${colors[reset]}"
}

print_error() {
    printf '%b %b%b%b\n' "${emojis[error]}" "${colors[red]}" "$*" "${colors[reset]}" >&2
}

print_warning() {
    printf '%b %b%b%b\n' "${emojis[warning]}" "${colors[yellow]}" "$*" "${colors[reset]}"
}

print_info() {
    printf '%b %b\n' "${emojis[info]}" "$*"
}

print_debug() {
    [[ -n "${DEBUG:-}" ]] && printf '%b %b%b%b\n' "${emojis[debug]}" "${colors[blue]}" "$*" "${colors[reset]}"
}

Níveis de Log

Implementa níveis de log configuráveis.

Exemplos de código

Detecção de TTY

Desabilita cores em ambientes não interativos:

setup_colors() {
    if [[ -t 1 ]] && [[ -z "${NO_COLOR:-}" ]]; then
        # Terminal suporta cores
        COLOR_RED=$'\033[0;31m'
        COLOR_GREEN=$'\033[0;32m'
        COLOR_YELLOW=$'\033[1;33m'
        COLOR_BLUE=$'\033[0;34m'
        COLOR_RESET=$'\033[0m'
    else
        # Sem suporte a cores
        COLOR_RED=''
        COLOR_GREEN=''
        COLOR_YELLOW=''
        COLOR_BLUE=''
        COLOR_RESET=''
    fi
}

# Ambientes CI frequentemente suportam cores
detect_color_support() {
    if [[ -n "${CI:-}" ]] || [[ -n "${GITLAB_CI:-}" ]] || [[ -n "${GITHUB_ACTIONS:-}" ]]; then
        return 0  # Ambiente CI, habilita cores
    elif [[ -t 1 ]]; then
        return 0  # Terminal, habilita cores
    else
        return 1  # Sem suporte a cores
    fi
}

Seções Retráteis do GitLab CI

Cria seções de log retráteis no GitLab CI:

section_start() {
    local section_key="\${1:-section}"
    local section_header="\${2:-$section_key}"
    local collapsed="\${3:-true}"

    if [[ -n "${GITLAB_CI:-}" ]]; then
        printf "\e[0Ksection_start:%s:%s[collapsed=%s]\r\e[0K%s\n" \
            "$(date +%s)" "$section_key" "$collapsed" "$section_header"
    else
        printf '\n=== %s ===\n' "$section_header"
    fi
}

section_end() {
    local section_key="\${1:-section}"

    if [[ -n "${GITLAB_CI:-}" ]]; then
        printf "\e[0Ksection_end:%s:%s\r\e[0K" "$(date +%s)" "$section_key"
    else
        printf '\n'
    fi
}

# Uso
section_start "build" "Construindo Aplicação"
make build
section_end "build"

Agrupamento do GitHub Actions

Exemplos de código

Indicadores de Progresso

Exemplos de código

Logging Estruturado de Etapas

Exemplos de código

Biblioteca de Logging Shlocksmith

Para logging abrangente com integração total de CI, use a biblioteca de logging shlocksmith.

Recursos

  • Mais de 20 funções de nível de log (log_info, log_error, log_warning, etc.)
  • Logging baseado em etapas (log_step_start, log_step_pass, log_step_fail)
  • Suporte a cores e emojis com detecção de TTY
  • Gerenciamento de seções do GitLab CI
  • Caracteres de desenho de caixa para TUI
  • Formatação de pares chave-valor

Funções Disponíveis

# Logging básico
log_info "Mensagem informativa"
log_warning "Mensagem de aviso"
log_error "Mensagem de erro"
log_debug "Mensagem de depuração"  # Exibido apenas quando DEBUG está definido
log_notice "Mensagem de notificação"
log_fatal "Erro fatal"    # Encerra o script

# Logging baseado em etapas
log_start "Nome do processo"
log_step_start "Descrição da etapa"
log_step_pass "Mensagem de sucesso"
log_step_fail "Mensagem de falha"
log_step_skip "Mensagem de pulo"
log_step_done "Mensagem de conclusão"
log_done "Processo completo"

# Resultados
log_pass "Teste aprovado"
log_fail "Teste falhou"
log_result "Detalhes do resultado"
log_success "Mensagem de sucesso"

# Seções de CI
section_start "section_id" "Título da Seção"
section_end "section_id"

Uso

#!/usr/bin/env bash
source /caminho/para/log_functions.sh

log_start "Processo de Implantação"

section_start "deps" "Instalando Dependências"
log_step_start "Instalando pacotes"
if apt-get install -y pacote; then
    log_step_pass "Pacotes instalados"
else
    log_step_fail "Falha na instalação de pacotes"
fi
section_end "deps"

log_done "Implantação concluída"

Recursos Adicionais

Scripts

Referência de Cores

CódigoCor
\033[0;30mPreto
\033[0;31mVermelho
\033[0;32mVerde
\033[0;33mAmarelo
\033[0;34mAzul
\033[0;35mMagenta
\033[0;36mCiano
\033[0;37mBranco
\033[1;XXmVariante negrito
\033[0mReset

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