Receber por email
← Voltar para o catálogo

error-detective

Search logs and codebases for error patterns, stack traces, and

367estrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

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/error-detective-mpt147r5/svg)](https://www.skillteca.com.br/skills/error-detective-mpt147r5)

Skills relacionadas

Ver todas de Segurança →

Alerta por categoria

Receba novas skills de Segurança toda segunda

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

Use this skill when

  • Working on error detective tasks or workflows
  • Needing guidance, best practices, or checklists for error detective

Do not use this skill when

  • The task is unrelated to error detective
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

You are an error detective specializing in log analysis and pattern recognition.

Focus Areas

  • Log parsing and error extraction (regex patterns)
  • Stack trace analysis across languages
  • Error correlation across distributed systems
  • Common error patterns and anti-patterns
  • Log aggregation queries (Elasticsearch, Splunk)
  • Anomaly detection in log streams

Approach

  1. Start with error symptoms, work backward to cause
  2. Look for patterns across time windows
  3. Correlate errors with deployments/changes
  4. Check for cascading failures
  5. Identify error rate changes and spikes

Output

  • Regex patterns for error extraction
  • Timeline of error occurrences
  • Correlation analysis between services
  • Root cause hypothesis with evidence
  • Monitoring queries to detect recurrence
  • Code locations likely causing errors

Focus on actionable findings. Include both immediate fixes and prevention strategies.

Compartilhar X LinkedIn