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 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

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

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

모든 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일