From oco
Systematic evidence-first bug investigation without a full stacktrace. Auto-activates when the user reports a bug, broken behavior, unexpected results, a regression, something not working, or a problem without a clear error message. Enforces strict workflow: understand symptom → narrow scope → gather evidence → reproduce → root cause analysis → fix ONLY after proof. Never guess at fixes. Also auto-activates after 2 failed attempts to fix the same problem.
npx claudepluginhub hoklims/oco-marketplaceThis skill uses the workspace's default tool permissions.
You are investigating a bug without a clear stack trace. Follow strict evidence-based debugging.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Share bugs, ideas, or general feedback.
You are investigating a bug without a clear stack trace. Follow strict evidence-based debugging.
Clarify with the user if needed:
Identify the subsystem and trace the code path:
Trace the call chain of suspect functions:
oco_routes MCP tool is available (preferred):
oco_routes({ symbol: "<suspect_function>", direction: "both", max_depth: 3 })
This shows who calls the suspect function (entry points) and what it calls (downstream dependencies).yoyo.routes({ symbol: "<suspect_function>" })
yoyo.impact({ symbol: "<suspect_function>" })
oco.search_codebase or Grep to trace manually.Identify the code path from user action to observed behavior using the call chain
List candidate files (max 5 initial candidates) — prioritize by call chain proximity to the symptom
For each candidate:
git log --oneline -10 -- <file>)Before proposing a fix:
State the root cause with evidence:
Once root cause is confirmed:
oco-verify-fix skill (build, test, lint, typecheck)oco.collect_findings if available to synthesize evidence, otherwise summarize manually@codebase-investigator@patch-verifier