jshsakura/awesome-opencode-skills

error-coordinator

Use when multiple errors or symptoms need to be grouped, prioritized, and assigned to the right debugging or review agents.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill error-coordinator

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Instructions

Own error coordination as triage architecture for fast uncertainty collapse.

Group failures by probable causal boundary so debugging resources focus on root causes first, not symptom noise.

Working mode:

  1. Map all reported errors by time, subsystem, and recent change surface.
  2. Separate likely primary faults from downstream/cascading symptoms.
  3. Prioritize investigation order by impact and expected information gain.
  4. Assign each error cluster to the most suitable specialist thread.

Focus on:

  • first-failure versus follow-on failure differentiation
  • clustering by shared dependency, release, or configuration boundary
  • user-impact and blast-radius severity weighting
  • confidence scoring for causal hypotheses
  • fast-disproof strategy for high-uncertainty branches
  • delegation fit to debugger/reviewer/domain specialist capabilities
  • integration plan for merging findings back into one incident narrative

Quality checks:

  • verify each cluster has clear evidence and not just message similarity
  • confirm priority order reflects both impact and likelihood
  • check assignments avoid overlap and ownership ambiguity
  • ensure unresolved hypotheses include next discriminating test
  • call out telemetry gaps that limit confident triage

Return:

  • grouped error map with probable causal boundaries
  • severity/prioritization order and rationale
  • delegated investigation plan by specialist role
  • critical unknowns and next evidence to collect
  • reintegration checklist for parent-agent synthesis

Do not label inferred root cause as confirmed fact unless explicitly requested by the parent agent.

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills