Menu
SkillsMP has collected 15 skills from hoklims/oco. Open a skill to review its source and details.
Showing 15 of 15 collected skills.
Orchestrated coding workflow — the unified entry point for all OCO capabilities. Use when the user types /oco followed by any request, or when a task would benefit from structured orchestration combining code intelligence, impact analysis, verification, and…
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:…
Structured refactoring with impact analysis, staged changes, and verification. Auto-activates when the user asks to refactor, rename, restructure, extract, move, reorganize, decouple, or split code. Enforces a strict workflow: impact analysis before any…
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…
Mandatory verification suite after any code change. Auto-activates after every source file modification, even trivial ones (one-liner). Detects project type (Cargo.toml, package.json, pyproject.toml, go.mod, .csproj) and runs in order: build → types → lint →…
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:…
Structured refactoring with impact analysis, staged changes, and verification. Auto-activates when the user asks to refactor, rename, restructure, extract, move, reorganize, decouple, or split code. Enforces a strict workflow: impact analysis before any…
Orchestrated coding workflow — the unified entry point for all OCO capabilities. Use when the user types /oco followed by any request, or when a task would benefit from structured orchestration combining code intelligence, impact analysis, verification, and…
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…
Mandatory verification suite after any code change. Auto-activates after every source file modification, even trivial ones (one-liner). Detects project type (Cargo.toml, package.json, pyproject.toml, go.mod, .csproj) and runs in order: build → types → lint →…
Structured codebase exploration with OCO-backed code intelligence. Auto-activates when the user asks to explore, understand, explain how a module works, a feature, an architecture, a data flow, or asks "how does this work", "where is", "show me", "what is…
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:…
Structured refactoring with impact analysis, staged changes, and verification. Auto-activates when the user asks to refactor, rename, restructure, extract, move, reorganize, decouple, or split code. Enforces a strict workflow: impact analysis before any…
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…
Mandatory verification suite after any code change. Auto-activates after every source file modification, even trivial ones (one-liner). Detects project type (Cargo.toml, package.json, pyproject.toml, go.mod, .csproj) and runs in order: build → types → lint →…