lingzhi227/agent-research-skills

code-debugging

Debug experiment code with structured error analysis.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/lingzhi227/agent-research-skills --skill code-debugging

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

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

Code Debugging

Systematically debug experiment code with structured error categorization and fix strategies.

Input

  • $0 — Error message, stderr output, or code file with issues
  • $1 — Optional: the code that produced the error

References

  • Debug patterns and state machine: ~/.claude/skills/code-debugging/references/debug-patterns.md

Workflow

Step 1: Categorize the Error

CategoryExamplesSeverity
SyntaxErrorInvalid syntax, indentationLow
ImportErrorMissing module, wrong nameLow
RuntimeErrorDivision by zero, shape mismatchMedium
TimeoutErrorInfinite loop, too slowMedium
OutputErrorMissing files, wrong formatMedium
LogicErrorWrong results, 0% accuracyHigh

Step 2: Analyze Root Cause

  1. Read the error traceback (last 1500 chars if truncated)
  2. Identify the exact line and variable causing the error
  3. Check for common patterns:
  • Device mismatch (CPU vs GPU tensors)
  • Shape mismatch in matrix operations
  • Missing data normalization
  • Off-by-one errors in indexing
  • Incorrect loss function for task type

Step 3: Apply Fix Strategy

For syntax/import errors: Direct fix, single attempt For runtime errors: Fix and rerun, up to 4 retries For logic errors: Reflect on approach, consider alternative methods For timeout: Reduce dataset size, optimize bottleneck, add early stopping

Step 4: Reflect and Prevent

After fixing:

  1. Explain why the error occurred
  2. Identify which lines caused it
  3. Describe the fix line-by-line
  4. Note patterns to avoid in future code

Fix Strategy State Machine

Stage 0 (first attempt) → repost code as fresh
Stage 1 (second attempt) → repost or leave depending on severity
Stage 2 (third attempt) → regenerate from scratch if still failing

Rules

  • Prefer minimal targeted edits over full rewrites
  • Maximum 4-5 fix attempts before changing approach
  • Always truncate long error outputs to last 1500 characters
  • After fixing, verify the fix doesn't introduce new errors
  • Keep error history to avoid repeating the same mistakes
  • If 0% accuracy: check accuracy calculation first, then check data pipeline

Related Skills

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills