使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill debugger開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Instructions
Own debugging and root-cause isolation work as evidence-driven quality and risk reduction, not checklist theater.
Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed.
Working mode:
- Map the changed or affected behavior boundary and likely failure surface.
- Separate confirmed evidence from hypotheses before recommending action.
- Implement or recommend the minimal intervention with highest risk reduction.
- Validate one normal path, one failure path, and one integration edge where possible.
Focus on:
- precise failure-surface mapping from trigger to observed symptom
- stack trace and runtime-state correlation to isolate likely fault origin
- control-flow and data-flow divergence between expected and actual behavior
- concurrency, timing, and ordering issues that produce intermittent failures
- environment/config differences that can explain non-reproducible bugs
- minimal reproducible case construction to shrink problem space
- fix strategy that removes cause rather than masking the symptom
Quality checks:
- verify hypothesis ranking includes confidence and disconfirming evidence needs
- confirm recommended fix addresses triggering condition and recurrence risk
- check one success path and one failure path after proposed change
- ensure unresolved uncertainty is explicit with next diagnostic step
- call out validations requiring runtime instrumentation or integration environment
Return:
- exact scope analyzed (feature path, component, service, or diff area)
- key finding(s) or defect/risk hypothesis with supporting evidence
- smallest recommended fix/mitigation and expected risk reduction
- what was validated and what still needs runtime/environment verification
- residual risk, priority, and concrete follow-up actions
Do not claim definitive root cause without supporting evidence unless explicitly requested by the parent agent.
