Scan a request, document, or conversation for ambiguities, undefined terms, implicit assumptions, and unstated boundaries, then surface them as a certainty-tiered findings report with recommended defaults. Use when the user says "clarify", "what is ambiguous here", "find the gaps in this spec", "what am I assuming"…
Run the repo hygiene skills over your own just-changed output before handing it back, routing to whichever the change earned among rewrite-clean-v0, debloat, shower, reorder, verify-both-ways, consolidate-to-one-home, and unslop. Use automatically after editing a durable artifact, or when the user says "clean and…
Reduce internal duplication, dead code, and ceremony. Use when you spot dead fields, redundant wrappers, or speculative abstractions in code you are already editing.
Shared vocabulary for designing deep modules: module, interface, implementation, depth, seam, adapter, leverage, locality. Use when designing or improving a module interface, deciding where a seam goes, making code more testable, or when another skill needs the deep-module terms.
Commit working-tree changes and push to the current branch: no branch creation, no branch switch, no PR. Use when asked to push to the branch you are already on, including the default branch.
Use when a verified non-trivial outcome should be written up as a docs/solutions/ entry or a CONCEPTS.md term, and the user asks for it explicitly. Fires only on request; for automatic capture after a verified fix, use autolearn.
Fold a scattered fact into a single home and point the rest at it. Use when the same rule, constant, or definition is restated in several files, or the user says "consolidate this", "make this the single source of truth", or "ssotize this". The consolidation is proposed and approved before any edit lands. To…
Design-by-Contract (DbC). Use when crossing public API boundaries, guarding complex state invariants, or hardening untrusted inputs and integration seams.
Compress a bloated artifact to its load-bearing density, cutting words and never a rule. Use when a document, skill, or spec has grown padded while every rule in it still binds, or the user says "debloat this", "tighten this up", or "this is too long". Every rule present before the pass is present after it. To cut…
Use when the user has a fork and wants it resolved and applied, not explored: "help me decide", "just decide this", "what should I do here", "decide and fix it". Frames each fork as one single-select with a recommended default, takes the pick, and applies it. Requirement exploration that ends in a document goes to…
Ledger-first dedup of a skills/ or prompt-directory tree. Use when the user asks to dedup skills, find rules repeated across or within skill files, or check whether skills contradict each other.
Dependency-upgrade campaign. Use when CVEs require remediation, a major upstream version lands, stack compatibility forces a sweep, on a scheduled hygiene cadence, or for a lockfile audit before a release.
Certainty-graded cleanup of code debris. Use when the user says "deslop", "remove debug code", "find placeholders or stub code", or "remove dead code", or when the slop skill routes code findings here.
Use when a diagram is going into a document: pick the tool, write the text source, render it, and embed it with an accessible caption. Text DSL plus a committed SVG is the shape — nomnoml for structure and flow, D2 for architecture, the house palette on both.
Ship the whole ask in one pass. Use when work would otherwise be split into phases, staged rollouts, follow-up PRs, or TODO-later remainders, or when the user says ship it now, no phases, or do it now.
Document decisions, not just code. Use when making architectural decisions, changing public APIs, shipping features, or capturing context for future engineers and agents.