← Voltar para o catálogo
Estruturas de análise de causa raiz, incluindo investigação baseada em logs, correlação com git bisect e diagnóstico baseado em padrões com pontuação de confiança.
Ver no GitHub ↗
Copiar URL do repo
Copiar link do SKILL.md Licença: MIT
Como adicionar
Copiar comando
/plugin marketplace add a5c-ai/babysitter
O comando exato pode variar conforme o repositório. Confira o README no GitHub.
Para o autor da skill
Cole no README do seu repo
Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.
[](https://www.skillteca.com.br/skills/debugging-patterns)
Copiar snippet
利用AI大模型，一键生成高清短视频 Generate short videos with one click using AI LLM.
Automação
por harry0703
Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.
Automação
#ai
por shanraisshan
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
Automação
#git
#github
por sickn33
Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.
Automação
#git
#github
por sickn33
Alerta por categoria
1 email curto, só com as skills novas de Automação. 4 minutos de leitura, sem spam, cancela com 1 clique.
Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.
Ler descrição completa Recolher descrição Debugging Patterns
Overview
Provides structured frameworks for root cause analysis. The log-first methodology ensures evidence is gathered before hypotheses are formed.
Log-First Investigation
Read ALL available logs, error output, and stack traces DO NOT form hypotheses before reading evidence Identify the exact error: message, file, line, call stack Determine reproduction steps from evidence Check git log for recent changes correlating with bug introduction Pattern-Based Diagnosis
Check patterns.md for known gotchas matching the error Cross-reference with common patterns: null pointer, race condition, resource leak, config error Rate root cause confidence (>=80% to proceed with fix) Evidence Collection
Stack traces with full call chain Error messages with context Exit codes from reproduction attempts Git blame/log for change correlation Environment differences (if applicable) When to Use
During DEBUG workflow investigation phase When BUILD tests fail unexpectedly When reviewing error handling gaps Agents Used
bug-investigator (primary consumer)silent-failure-hunter (pattern reference)
Compartilhar
X
LinkedIn
Copiar link
