From oco
Stack trace and runtime error analysis to identify root cause. Auto-activates when the user pastes a stacktrace, traceback, panic, exception, crash, or error with line number. Also detects runtime errors in command output (build, test, run). Enforces workflow: parse trace → map to code → inspect suspect regions → ranked hypotheses → verify before fixing. Never propose a fix without reading the failing code.
npx claudepluginhub hoklims/oco-marketplaceThis skill uses the workspace's default tool permissions.
You are analyzing a runtime error or stack trace. Follow this evidence-based workflow.
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 analyzing a runtime error or stack trace. Follow this evidence-based workflow.
Extract from the error:
Use oco.trace_error if available (parses frames, maps to codebase, identifies root cause regions):
oco.trace_error({ stacktrace: "<paste stacktrace>", workspace: "." })
Enrich with call graph — trace the call chain around the error site:
oco_routes MCP tool is available:
oco_routes({ symbol: "<failing_function>", direction: "both", max_depth: 3 })
This reveals the full call path to the error (callers = how we got here, callees = what failed downstream).yoyo.routes({ symbol: "<failing_function>" })
Otherwise, manually inspect the files referenced in the stack trace using Read, starting from the deepest application frame (skip library/framework frames).
For each candidate location:
Produce 1-3 ranked hypotheses:
Do NOT propose a fix until you have:
@codebase-investigatoroco-verify-fix skill (build, test, lint, typecheck)oco.collect_findings if available to synthesize evidence, otherwise summarize manually