audit

Quality, Risk & Design Audit

/audit is THE read-only analysis entry point for this plugin. It subsumes every separate analysis path — there is one front door, one selector grammar, and one unified report. It resolves a selector against the glossary, delegates the heavy lifting to the oop-orchestrator, and returns a single merged report. It assumes nothing about the language or stack and never modifies code.

The plugin organizes analysis across two tracks and zooms through three layers — track → aspect → family / category / entity:

• RISK track — find problems: code smells, antipatterns, vulnerabilities, supply-chain risks.
• PATTERN track — work with design patterns: detect patterns already present (pattern-scan) and suggest the most-suitable patterns where one would help (pattern-fit).

A full /audit runs both tracks in parallel and merges them into ONE report.

Selector grammar

/audit [full | changed | component <path>]            → L1: both tracks, in parallel, one report
/audit risks [scope]                                  → L2: RISK track only
/audit patterns [scope]                               → L2: PATTERN track (scan + fit)
/audit pattern-scan [scope]                           → aspect: patterns already present
/audit pattern-fit [scope]                            → aspect: most-suitable pattern suggestions
/audit <category> [scope]                             → one issue/pattern category
/audit <family> [scope]                               → one family of issues or patterns
/audit <entity-id> [scope]                            → one entity or pattern

Every form takes an optional scope suffix — full (default), changed, or component <path>.

What to look for (selector, default = both tracks)

The glossary is the single source of truth for what the plugin recognizes. A selector resolves against it, zooming from the broadest layer (a whole track) to the narrowest (one entity):

• full / changed / component <path> / none — the L1 full run: the RISK track and the PATTERN track dispatched in parallel, merged into one unified report. (A bare scope word with no selector is the full run scoped accordingly.)
• risks — the RISK track only (its sole aspect is risk-scan): every issue family (oop, code, architecture, testing, concurrency, database, security, dependency).
• patterns — the PATTERN track: both aspects, pattern-scan + pattern-fit.
• pattern-scan — one aspect: design patterns already present in the code.
• pattern-fit — one aspect: the most-suitable patterns where one would help.
• <category> — one category of entities (e.g. vulnerability, antipattern, code-smell, supply-chain-risk, design-pattern).
• <family> — one family of issues or patterns (e.g. oop, security, behavioral). oop is the spine of this plugin — it surfaces whenever class/struct/interface declarations are present.
• <entity-id> — a single glossary entity or pattern, by its stable id (e.g. god-class, feature-envy, strategy).