poteto/noodle

debugging

Systematic root-cause debugging methodology.

소스 보기

사용 방법

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

시작 전 확인

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

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

Debugging

Read [[principles/fix-root-causes]] before starting. Every debugging session follows that principle: trace to root cause, never paper over symptoms.

Process

  1. Reproduce. Get the exact error. Run the failing command, read the full output. If you can't reproduce, you can't verify your fix.
  1. Read the error. The error message, stack trace, and line numbers are data. Read all of it before forming hypotheses. Most bugs tell you exactly where they are.
  1. Suspect state before code. Before debugging code, check persistent state — especially on restart bugs or environment drift. See [[principles/fix-root-causes]].
  • Noodle state: .noodle/orders.json (stale items?), .noodle/sessions/ (orphaned?), .noodle.toml (valid?)
  • Environment: tmux sessions (tmux ls), lock files, cached artifacts
  • Config: .noodle.toml validation (noodle start reports diagnostics), skill frontmatter parse errors
  • Persistent files: brain/ notes, plan files, todos — check for corruption or stale references
  1. Isolate. Narrow the scope. Which file? Which function? Which line? Use binary search: comment out half, see if it still fails, repeat.
  1. Find root cause. The first "fix" that comes to mind is usually a symptom fix. Ask "why?" until you hit the actual cause:
  • Test fails → mock is wrong → interface changed → type doesn't match runtime shape → fix the type
  • Build fails → import error → circular dependency → restructure the modules
  • Runtime crash → undefined value → missing null check → data source returns null on empty → handle empty case at the source
  1. Fix and verify. Fix the root cause, not the symptom. Then verify: run the test, run the build, exercise the feature path. "It compiles" is not verification.
  1. Check for the pattern. If the bug existed in one place, grep for the same pattern elsewhere. Fix all instances, or make it structurally impossible.

Noodle-Specific Diagnostics

When debugging Noodle infrastructure failures:

SymptomCheck first
Cook won't starttmux ls, .noodle/orders.json validity, skill resolver paths
Orders stuck.noodle/orders.json for stale items, .noodle.toml adapter config
Missing skill.noodle.toml [skills] paths, .agents/skills/<name>/SKILL.md exists
Stale mise.noodle/mise.json generated_at timestamp, backlog sync script
Session orphaned.noodle/sessions/<id>/meta.json status, tmux ls for zombie sessions

When Stuck

  • Instrument, don't guess. Add logging at key points to see actual values. Read actual state ([[principles/prove-it-works]]).
  • Diff what changed. git diff, git log, git bisect. Most bugs are recent.
  • Simplify. Strip the failing case to minimum reproduction. Remove everything unrelated.
  • Change one thing at a time. Multiple changes at once make it impossible to know what fixed (or broke) it.
  • Check assumptions. The bug is often in the part you're sure is correct. Verify everything.

Anti-Patterns

  • Bypass flags (--no-verify, --force, SKIP_CHECK=true) silence symptoms without fixing causes.
  • Retry loops hide intermittent bugs behind probability.
  • Shotgun debugging — changing three things to "see if it helps" — obscures causality.
  • Adding guards (if (x !== undefined)) without asking why x is undefined.

After Fixing

If this bug could recur or affected your understanding, capture the lesson. Write a brain note, update a skill, or add a todo. The system should get smarter from every bug. See [[principles/encode-lessons-in-structure]].

같은 저장소의 Skills

더 많은 Skills

모든 Skills
poteto
커뮤니티

reflect

Reflect on the conversation and update the brain. Use when wrapping up, after mistakes or corrections, or when significant codebase knowledge was gained. Triggers: "reflect", "remember this".

1시간 설치 수
1
GitHub Stars
646
업데이트
3월 19일
poteto
커뮤니티

unslop

Remove AI writing patterns from prose. Use for docs, READMEs, blog posts, any non-code text that should sound human. Triggers: "unslop", "humanize", "make this sound human", "clean up this writing", "edit for voice", "de-AI this text".

1시간 설치 수
1
GitHub Stars
646
업데이트
3월 19일
poteto
커뮤니티

adversarial-review

Adversarial code review using cross-model approach. Spawns reviewers on the opposing model (Claude uses Codex, Codex uses Claude) to challenge work from distinct critical lenses. Produces a synthesized verdict with findings and lead judgment. Triggers: "adversarial review".

1시간 설치 수
1
GitHub Stars
613
업데이트
3월 19일
poteto
커뮤니티

brain

Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers after debugging sessions, mistakes, corrections, architectural decisions, or any insight worth preserving across sessions. Use on 'add to brain', 'remember this', 'write a note', or brain/ modifications.

1시간 설치 수
1
GitHub Stars
613
업데이트
3월 19일