passung

Plugin passung from marketplace werkstoff in Anselmoo/werkstoff. Commands read from the repo's manifest — 11 days ago.

Slash commands (8)

• /passung:passung-align

  Apply the approved canonical form to every divergent site, in dependency-aware batches, in place

• /passung:passung-brief

  Synthesize discovery into a phased Consistency Brief — the approved plan /passung-align executes against

• /passung:passung-canonize

  Use after /passung-scan to decide which variant of a divergent convention is canonical, with a provenance-tracked Pattern Card each

• /passung:passung-map

  Renders analysis/<area>/consistency.json as a module x convention matrix. Use after /passung-scan has run, to see where divergence concentrates.

• /passung:passung-preflight

  Environment readiness check — analysis tooling, documented-convention sources, git history depth, build/test toolchain

• /passung:passung-scan

  Inventory internal pattern/style/architecture divergence — excludes documented conventions and version-deprecated idioms

• /passung:passung-status

  Where does harmonization of this area stand — artifact inventory, staleness, next step

• /passung:passung-verify

  Prove an alignment pass changed nothing observable — test-suite equivalence, doc-vs-code re-sync, no stray drift

Subagents (5)

• align-executor

  Applies an approved canonical pattern to ONE module of an in-flight alignment pass by following a proven pilot playbook — minimal diff, then runs that module's real tests to prove it. Refuses to align anything if no playbook exists yet. Write access is scoped to its own module's directory. Use only

• consistency-critic

  Adversarially reviews a proposed canonical Pattern Card or an applied alignment diff. Looks for forced consistency where real variation was warranted, unsound basis reasoning, and PASS verdicts that were rubber-stamped rather than re-derived. Use as the single contract judge in canonize and verify.

• equivalence-verifier

  Independently re-checks that an aligned module behaves identically to before alignment and that its docs/comments still match the code. Re-derives evidence from the diff and the module's tests rather than trusting the aligner's own report. Use as the verification pass after passung-align.

• pattern-analyst

  Surveys a live codebase to find how a given convention dimension (error handling, logging, docstrings, module layout, naming, test structure, ...) is actually handled, clustering distinct approaches into variants with file:line evidence and a maturity/recency read from git history. Use for discovery

• pattern-extractor

  Derives which variant of an undocumented, non-deprecated convention should become the canonical form — weighing frequency, maturity, and recency, and refusing to force a pick when the signal is genuinely tied. Use when a divergent dimension from consistency.json needs a Pattern Card.

Similar plugins