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.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill error-coordinator

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills