메뉴
Diagnose and fix bugs through systematic investigation, root cause analysis, and targeted validation. Use when something is broken, errors occur, performance degrades, or unexpected behavior manifests.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/CaptainCrouton89/.claude --skill fixing-bugs-systematically명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Defines required structure, frontmatter format, and best practices for SKILL.md files. Use BEFORE creating or editing any skill - this is the spec to follow, not optional reference.
Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.
Maintain project documentation synchronized with code. Keep feature specs, API contracts, and README current with init-project standards. Use when updating docs after code changes, adding new features, or ensuring documentation completeness.
| name | Fixing Bugs Systematically |
| description | Diagnose and fix bugs through systematic investigation, root cause analysis, and targeted validation. Use when something is broken, errors occur, performance degrades, or unexpected behavior manifests. |
Structured protocol for isolating root causes and implementing focused fixes in existing features.
Read relevant documentation:
docs/feature-spec/F-##-*.md for affected featuredocs/user-stories/US-###-*.md for expected behavior and acceptance criteriadocs/api-contracts.yaml if API-relateddocs/system-design.md for architecture contextDocument the bug:
Use direct investigation:
Delegate to async agents in parallel:
Spawn agents to:
senior-engineerSpawn Explore agents to:
Example: For authentication bug, spawn:
Wait for results using ./agent-responses/await {agent_id}
Generate hypotheses:
Decision point:
Add minimal debugging:
Test to confirm root cause before proceeding to fix.
Fix the confirmed root cause:
Update documentation if needed:
docs/api-contracts.yaml if contract changed (requires approval)/manage-project/update/update-feature to correct spec/manage-project/update/update-story if ACs were ambiguous/manage-project/update/update-api if API changed (with approval)Verify fix against acceptance criteria:
docs/data-plan.md still fire correctlyFor direct investigation:
When to validate before fixing:
For async investigation:
Inputs:
docs/feature-spec/F-##-*.md — Feature specsdocs/user-stories/US-###-*.md — Expected behavior and ACsdocs/api-contracts.yaml — API specsdocs/system-design.md — Architecture contextOutputs:
| Scenario | Approach |
|---|---|
| Single subsystem, obvious entry | Direct investigation → immediate fix |
| Multiple subsystems, unclear origin | Spawn 2-4 agents in parallel → synthesize findings → fix |
| Runtime-dependent or intermittent | Add targeted logging → reproduce → analyze logs → fix |
| Multiple independent fixes needed | Pass investigation results to fix agents via artifact files |