Auto-enforcing loop that walks a project's value stream — its stages and the wires between them — closing one gap per stage and refusing to advance past a broken or unproven wire (the andon rule). Composes andon-propose (pick and design the fix) and andon-verify (prove the wire) over a native OKF ledger. Use this when the user wants to "harden this repo", "run the andon loop", "scan for gaps and fix them in order", "prove this wire is proven", "resume the andon ledger", or any request to iterate a multi-stage codebase closing gaps while keeping each handoff evidence-grounded rather than assumed.
Checks whether the current repository has a legible multi-stage value stream and where the andon ledger should live. Detects stage/wire legibility (directly or via self-assess:stage-mapper if installed), checks for a house-rules.md andon-propose can draw defaults from, and confirms an output/ledger location is writable. Use this when the user asks "is my repo ready for andon", "can andon-loop run here", "check if andon can find my stages", or before running andon-propose, andon-verify, or andon-loop for the first time in a repo.
Runs a complex, ambiguous, or multi-faceted task through compass's full Clarify -> Explore -> Decompose -> Execute -> Revise pipeline, composing the plugin's other 12 skills as pipeline stages instead of requiring the user to invoke them individually. Use when a task is genuinely large enough to need staged decomposition AND carries real ambiguity or multiple viable approaches worth weighing before committing — "solve this end-to-end, I'm not sure of the best approach", "plan this out and carry it out, here are the constraints", or a request that would otherwise mean chaining several compass-* skills by hand. Do not use for a single well-scoped question, a task with one obvious approach and nothing to decompose, or anything answerable directly — most requests do not need this skill; each of compass's other 12 skills stays independently invocable for a narrower job that doesn't warrant the full pipeline.
This skill should be used when the user asks to "check for type signature drift", "verify our API schema matches the handler", "audit our function signatures for drift", "find mismatched function contracts", "check if type hints match how functions are actually called", or "audit our OpenAPI/GraphQL schema against the code". Extracts machine-checkable contracts (type hints, function signatures, docstring parameter/return descriptions, API/OpenAPI/GraphQL schemas) from source files and checks each against actual call-site and handler usage, reporting contradictions with file:line evidence on both sides.
This skill should be used when the user asks to "run a quality self-optimization cycle", "harden the quality findings", "fix what quality found and re-check", "converge the quality audit", or wants the confab plugin's four domain audits run repeatedly with cross-run memory until they stop finding new things — optionally applying and re-verifying fixes for dependency-hallucination, contract-drift, and mechanical agentic-reliability findings, and drafting (never applying) assertion-strength suggestions.
This skill should be used when the user asks to "check for hallucinated dependencies", "verify our packages actually exist", "audit dependencies for AI-generated code", "does this package actually exist on npm/PyPI", or wants declared dependencies in manifest files (package.json, requirements.txt, pyproject.toml, Cargo.toml, go.mod, Gemfile) cross-checked against their real public registries for non-existent or typosquat-adjacent packages.
Checks whether the current repository is ready for the confab plugin's audit skills to run well. Detects declared-dependency manifests, probes reachability of each detected language's public package registry, and checks for a real mutation-testing tool on PATH. Use this when the user asks to "run quality preflight", "check if the confab plugin can run here", "is my repo ready for a dependency audit", or before running confab-dependency-audit, confab-assertion-audit, confab-contract-drift, or confab-agentic-reliability for the first time in a repo.
Audits this repository's git remotes, CI configuration, any publish/mirror scripts, and commit-signing consistency for redundant remotes, doc-vs-reality drift about CI, one-directional force-push mirrors with no reverse-sync path, and inconsistent commit signing (the green "Verified" vs grey "Unverified" badge — some commits signed, some not, or `commit.gpgsign` unset). Use this when the user asks to check our git remotes, audit CI setup, find redundant mirrors, verify the docs about CI/CD are accurate, or check commit signing / why some commits show grey/unverified / provenance (CI/git-topology claims only — for broader doc-vs-code drift on other topics, use self-assess-docs-drift).