debugging
デバッグの原則。仕様とログから範囲を絞り込む。
When & Why to Use This Skill
This Claude skill provides a systematic framework for software debugging, focusing on narrowing down issue scope through specification review and log analysis. It guides developers through a structured four-step investigation process—clarifying requirements, isolating failures via logs, researching historical precedents, and performing code-level analysis—to ensure efficient problem resolution and comprehensive documentation of root causes.
Use Cases
- Isolating Software Defects: Systematically narrowing down the source of a bug by comparing execution logs against technical specifications to identify exactly where the logic fails.
- Standardizing Debugging Workflows: Implementing a consistent investigation sequence across engineering teams to reduce mean time to resolution (MTTR) and improve troubleshooting efficiency.
- Root Cause Analysis & Documentation: Recording detailed insights including the gap between expected and actual behavior, fundamental causes, and implemented fixes for future knowledge sharing.
| name | debugging |
|---|---|
| description | デバッグの原則。仕様とログから範囲を絞り込む。 |
デバッグの原則
調査の順序
- 期待する動作を明確にする（仕様確認）
- ログから範囲を絞る（どこまで成功したか）
- 過去の類似例を探す
- コードを調査する
記録すべき情報
- 期待する動作 vs 実際の動作
- 根本原因
- 修正内容