alexbruno/dev-skills

systematic-debugging

Investigate bugs and failures through disciplined root-cause analysis before writing fixes.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/alexbruno/dev-skills --skill systematic-debugging

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

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

Systematic Debugging

Find and prove the root cause before changing any production code. Never guess, apply shotgun patches, or silence errors to make symptoms disappear.

Core Rule

No fix without a confirmed root cause. Every bug fix must follow: Reproduce -> Isolate -> Prove Root Cause -> Regression Test -> Fix -> Verify.

Debugging Process

1. Reproduce Reliably

  • Capture exact reproduction steps, inputs, environment conditions, and expected vs. actual behavior.
  • If the failure cannot be reproduced yet, gather logs, traces, or state snapshots first—do not speculate.

2. Isolate & Form Hypotheses

  • Narrow the failure boundary (recent changes via git diff/git log, failing inputs, or call paths via codebase-indexing if active).
  • Form one concrete, testable hypothesis at a time about why the failure occurs.
  • Test the hypothesis with targeted observation (logs, minimal reproduction, or debugger/test run).

3. Confirm & Document Root Cause

  • Confirm the exact mechanism causing the bug with direct evidence.
  • If workflow/SPEC.md is active for this bug fix, record the reproduction steps and confirmed root cause there before planning the fix.

4. Write a Failing Regression Test First

  • Create an automated test (or reproducible check) that fails for the exact reason of the bug.
  • Verify it fails before applying the fix so you know the test actually catches the regression.

5. Fix the Root Cause & Verify

  • Apply the minimal, clean fix that addresses the root cause—not a workaround around the symptom.
  • Run the regression test and the full relevant test suite to confirm no regressions were introduced.

Anti-Patterns to Avoid

  • Shotgun debugging: Changing multiple unrelated things at once hoping one works.
  • Symptom masking: Catching and ignoring exceptions, adding arbitrary retries/sleeps, or loosening assertions to pass tests.
  • Speculative fixes: Editing code before you can explain why it failed.
同じリポジトリから

関連する Skills

すべての Skills
alexbruno
コミュニティ

architect-worker

Role-based multi-agent software engineering pattern separating high-level architecture, specification, planning, and code review (Architect) from focused code implementation and verification (Worker). Use this skill whenever assigned the Architect or Worker role (in any language), or when coordinating work between planning/review agents and implementation agents via workflow/.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日
alexbruno
コミュニティ

changelog-management

Maintain and update a standardized root CHANGELOG.md following Keep a Changelog and Semantic Versioning. Use this skill to initialize or update changelog entries, categorize changes, prepare release cuts, and proactively prompt the user when notable changes warrant updating the changelog.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日
alexbruno
コミュニティ

code-review

Perform structured, multi-dimensional code reviews aligned with the spec-driven-workflow (workflow/SPEC.md, workflow/PLAN.md, workflow/REVIEW.md). Use this skill after implementing a feature or bug fix, before merging a PR, or when reviewing changes written by another agent or human.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日
alexbruno
コミュニティ

code-simplification

Simplify code for human readability, clarity, and directness without changing behavior. Use this skill after implementing a feature, during refactoring, or when addressing code review feedback—especially when code feels over-engineered, deeply nested, or takes unnecessary detours to do simple things.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日