oops
Infrastructure fix for broken builds, failed tests, stale state, and environment drift. Covers both user-project and Noodle-internal failures. Triggers when builds break, tests fail, state is stale, or environment drifts. Use on 'oops', 'fix the build', 'tests are failing', 'something broke', 'broken build'.
소스 정보
- 저장소
- poteto/noodle
- 최근 소스 활동
- 2026년 3월 19일 04:43
- 감지된 SKILL.md 언어
- 영어
- 스타
- 277
- 포크
- 16
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- oops
- description
- Infrastructure fix for broken builds, failed tests, stale state, and environment drift. Covers both user-project and Noodle-internal failures. Triggers when builds break, tests fail, state is stale, or environment drifts. Use on 'oops', 'fix the build', 'tests are failing', 'something broke', 'broken build'.
- schedule
- When infrastructure failures are detected (build breaks, test failures, stale Noodle state)
# Oops
Fix infrastructure failures. Applies to both user-project code and Noodle-internal state.
## Fix flow
**Reproduce -> Diagnose -> Fix -> Verify -> Commit**
### 1. Reproduce
Run the failing command. Capture exact error output. If intermittent, run multiple times to confirm.
### 2. Diagnose
**Suspect state before code.** Check in this order:
1. **Noodle state** — `.noodle/` files, queue consistency, config validity
2. **Environment** — Go version, missing deps, stale caches, tmux session health
3. **Config** — `.noodle.toml` (project root), `.agents/skills/` structure, `brain/` integrity
4. **Persistent files** — lock files, temp files, incomplete writes
5. **Code** — only after ruling out state and environment
### Principles
- [[fix-root-causes]]
- [[prove-it-works]]
Noodle-internal checklist:
- `.noodle/` state files: corrupt, stale, or inconsistent?
- Queue state: orphaned tasks, stuck sessions?
- Config: valid TOML, referenced paths exist?
- tmux sessions: zombie processes, detached sessions?
### 3. Fix
Trace to root cause. Never paper over symptoms.
After fixing, grep for the same pattern elsewhere — the bug may exist in multiple locations.
### 4. Verify
Run the original failing command. Confirm it passes. Run related tests to check for regressions.
### 5. Commit
Commit message describes the root cause, not symptoms.
```
# Good: fix(queue): stale lock file prevented task dequeue after crash
# Bad: fix: tasks not running
```
GitHub에서 보기