mcpField
O
oops

oops

github.com/potetoDevelopment564217 installsUpdated 32w ago
Repository

About oops

A troubleshooting skill for infrastructure failures in user projects and Noodle itself. It follows a reproduce, diagnose, fix, verify, and commit process, checking state and environment before code.

Key features

  1. 01Reproduces failures and captures errors
  2. 02Checks project state and configuration
  3. 03Investigates environment and persistent files
  4. 04Targets root causes
  5. 05Verifies fixes and related tests
  6. 06Commits with root-cause descriptions

Use cases

  1. 01Diagnosing a stuck task queue
  2. 02Tracing failures to stale state or configuration
  3. 03Verifying an infrastructure fix

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/poteto/noodle --skill oops

After installing, type/oopsin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported