From oco
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 → tests. Produces a PASS/FAIL/PARTIAL verdict. NON-NEGOTIABLE: never consider a change complete without running this skill. Also activates when the user asks to verify, test, validate, or check their changes.
npx claudepluginhub hoklims/oco-marketplaceThis skill uses the workspace's default tool permissions.
You are verifying that code changes are correct and complete. Follow this structured verification 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 verifying that code changes are correct and complete. Follow this structured verification workflow.
List all modified files:
git diff --name-only HEAD 2>/dev/null || git status --short
Detect the verification suite from project manifests:
| Signal | Build | Types | Lint | Test |
|---|---|---|---|---|
Cargo.toml | cargo build | cargo check | cargo clippy | cargo test |
package.json | npm run build | tsc --noEmit | npm run lint | npm test |
pyproject.toml | - | mypy . | ruff check . | pytest |
go.mod | go build ./... | go vet ./... | golangci-lint run | go test ./... |
Use oco.verify_patch if available (auto-detects project type and runs all checks):
oco.verify_patch({ workspace: "." })
Otherwise, read the project manifest and run checks manually. Prefer scripts from package.json when available.
Execute in order (stop on first failure):
For each step, report:
For each modified function/method, check whether its callers are covered by tests:
If oco_impact MCP tool is available:
oco_impact({ symbol: "<modified_function>", max_depth: 2 })
Check: are the transitive callers exercised by the test suite?
If oco_routes MCP tool is available:
oco_routes({ symbol: "<modified_function>", direction: "callers", max_depth: 2 })
If yoyo MCP is available:
yoyo.impact({ symbol: "<modified_function>" })
Flag any caller that is NOT covered by existing tests as a potential regression blind spot.
Produce a verification verdict:
VERDICT: PASS | FAIL | PARTIAL
- Build: [pass/fail/skip]
- Types: [pass/fail/skip]
- Lint: [pass/fail/skip]
- Tests: [pass/fail/skip]
- Impact coverage: [covered / gaps detected / skip (no call graph)]
- Missing coverage: [description if applicable]
If any check fails:
After all checks pass, the PostToolUse hook automatically detects verification commands (cargo test, npm test, etc.) and marks the session as verified. The Stop hook will then allow completion without warning.
No manual marker is needed — the hook system handles this automatically.