oc-bug-check

原文涵盖的主题

• Bug Check
• /oc-bugcheck — Command Reference
• Session Persistence (Checkpoint Protocol)
• Resume on Start
• Write on Finish
• How This Skill Fits the Pipeline
• The Check Suite
• Check 1: Type Safety

On first invocation, read references/orchestrator.md and follow its welcome protocol. Pre-commit QA gate. Runtime depends on the configured checks and project size. Catches the bugs, type errors, test failures, and anti-patterns that shouldn't make it into a commit — before they cost real debugging time downstream. This is NOT oc-code-auditor. Code-auditor runs a deep tri-agent sweep (Auditor → Fixer → Verifier) that takes 30+ minutes and produces a graded report. Bug-check is the metal detector at the door — fast and blunt: the gate verdict is PASS, FAIL, or UNSUPPORTED (a required check cannot run — never a pass). Individual checks may emit advisory WARN notes (e.g. "no test suite detected") that ride on a PASS as a count; in strict mode they become FAIL. Only PASS clears the commit. --all, strict, and lenient are arguments to the declared run and config verbs, not separate commands. -- The shared checkpoint schema, write rules and resume protocol live in references/checkpoint-protocol.md, bundled with this skill. This section adds only what is specific to oc-bug-check. Checkpoint: {project-dir}/.checkpoints/oc-bug-check.checkpoint.json When /oc-bugcheck is invoked: 1. Check for

这里只展示节选，请以完整原文和当前要求为准。