본문으로 건너뛰기
cccskills
무료GitHub에 공개

dev-debug

Investigate bugs by clarifying expected behavior, reproducing the problem, and testing possible causes. The skill helps prepare a fix plan with risks and validation steps before code changes begin.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

AI DevKit · Guide structured debugging before code changes by clarifying expected behavior, reproducing issues, identifying likely root causes, and agreeing on a fix plan with validation steps. Use when users ask to debug bugs, investigate regressions, triage incidents, diagnose failing behavior, handle failing tests, analyze production incidents, investigate error spikes, or run root cause analysis (RCA).

codeaholicguy/ai-devkit스타 1,654(GitHub 1,654 + cccskills 0)

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Reproducing a bug and documenting its environment
  • Investigating a regression or failing test
  • Triage of production incidents or error spikes
  • Preparing a root cause analysis and fix plan

포함된 파일(2)

  • SKILL.md2.8 KB
  • agents/openai.yaml315 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Local Debugging Assistant

Debug with an evidence-first workflow before changing code.

Hard Rule

  • Do not modify code until the user approves a selected fix plan.

Workflow

  1. Clarify
  • Restate observed vs expected behavior in one concise diff.
  • Confirm scope and measurable success criteria.
  • Before investigating, search for similar past incidents: npx ai-devkit@latest memory search --query "<observed behavior>" --tags "debug,root-cause"
  1. Reproduce
  • Capture minimal reproduction steps. For user-flow bugs, make the repro a dev-smoke check that fails before the fix and passes after.
  • Capture environment fingerprint: runtime, versions, config flags, data sample, and platform.
  1. Hypothesize and Test For each hypothesis, include:
  • Predicted evidence if true.
  • Disconfirming evidence if false.
  • Exact test command or check.
  • Prefer one-variable-at-a-time tests.
  1. Plan
  • Present fix options with risks and verification steps.
  • Recommend one option and request approval.

Validation

  • Confirm a pre-fix failing signal exists.
  • Confirm post-fix success using the verify skill — including regression verification for bug fixes.
  • Summarize remaining risks and follow-ups.
  • Offer dev-retro to prevent recurrence; run only if the user agrees.
  • Store root cause and fix for future sessions: npx ai-devkit@latest memory store --title "<root cause>" --content "<diagnosis and fix>" --tags "debug,root-cause"

Task Tracing

If task tracing is usable, choose a short kebab-case debug task name when no task name exists, then use task optionally: record repro/final results as evidence, the current hypothesis as next, and blockers only when they materially affect progress. Never block debugging because task tracing is unavailable.

Red Flags and Rationalizations

RationalizationWhy It's WrongDo Instead
"I already know the cause"Assumptions skip evidenceReproduce and prove it first
"This is urgent, just fix it"A wrong fix wastes more time10 minutes of diagnosis saves hours
"The fix is obvious from the stack trace"Stack traces show symptoms, not causesTrace backward to the root cause

Output Template

Use this response structure:

  • Observed vs Expected
  • Repro and Environment
  • Hypotheses and Tests
  • Options and Recommendation
  • Validation Plan and Results
  • Open Questions

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Find active Codex, Claude Code, and other AI agents, inspect their recent context, and exchange messages with them. Use it to locate an agent, share information, or send a request and wait for a reply through ai-devkit commands.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Finding an active agent by name or status
  • Checking an agent’s recent context before contacting it
  • Sending information or requesting a reply from another agent
codeaholicguy/ai-devkit1.7천2026년 10월 25일 업데이트

Manage running AI agents with ai-devkit commands: identify sessions, list and inspect agents, start workers, assign or group tasks, resume sessions, and stop agents. The skill helps track assignments and verify completed work before reporting it.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • List agents and identify the current session
  • Inspect an agent before assigning work
  • Start a worker and delegate a task
codeaholicguy/ai-devkit1.7천2026년 10월 25일 업데이트

Coordinate ongoing work across multiple agents by checking progress, resolving dependencies, unblocking agents, relaying relevant results, and verifying completion. Use it to supervise a shared workflow across repeated check-ins.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Coordinating agents with dependent tasks
  • Unblocking an agent waiting for input
  • Relaying results between agents
codeaholicguy/ai-devkit1.7천2026년 10월 25일 업데이트

Check whether AI DevKit is ready on the local machine, identify setup gaps it can address, and run the narrowest relevant setup for supported agent harnesses. Recheck status afterward and report remaining manual actions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Check whether local AI DevKit setup is ready
  • Set up missing supported agent integrations
  • Review remaining setup steps after onboarding
codeaholicguy/ai-devkit1.7천2026년 10월 25일 업데이트

Explore ideas for products, content, names, strategies, technical approaches, or decisions. It frames the goal and constraints, generates distinct options, challenges assumptions and tradeoffs, then narrows the result to three strong choices with reasons and a next step.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Generating and comparing product or project ideas
  • Exploring names, content angles, or campaign concepts
  • Pressure-testing technical approaches or important decisions
codeaholicguy/ai-devkit1.7천2026년 10월 25일 업데이트

changelog

무료

Update the top Unreleased section of CHANGELOG.md using commits since the latest release. Add one concise linked line per commit, using a pull request link when evidence is clear and a commit link otherwise, while preserving the file’s existing style.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding recent commits to an Unreleased changelog
  • Creating release notes from commits since the last release
  • Linking changelog entries to their commits or pull requests
codeaholicguy/ai-devkit1.7천2026년 10월 25일 업데이트

codeaholicguy의 스킬 모두 보기

이 스킬의 문제 신고