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枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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