Receber por email
← Voltar para o catálogo

debug-complex-issue

Loop workflow for debugging a complex issue you've been stuck on for more than 30 minutes. Runs systematic hypothesis formation (debugging skill), feedback-loop mapping when the bug looks like a dynamic problem (systems-thinking), context-pathology check when it's an LLM/agent bug (context-degradation), blast-radius assessment before any fix attempt (risk-management), and uses test-driven-developm

9estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add viktorbezdek/skillstack

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.

[![Skillteca](https://www.skillteca.com.br/api/badge/debug-complex-issue/svg)](https://www.skillteca.com.br/skills/debug-complex-issue)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 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

Debug Complex Issue

Most complex bugs aren't complicated — they're just resistant to the first hypothesis you form. This workflow replaces hunting with a deliberate loop that forces evidence before every attempted fix.

Stuck debugging usually means the bug has a property the debugger hasn't noticed yet: it's timing-dependent, state-dependent, environment-dependent, or the result of a feedback loop that's invisible from any single stack trace. This workflow surfaces that property.

[Description truncada. Veja o README completo no GitHub.]

Compartilhar X LinkedIn