omen-reporting

Plugin omen-reporting from marketplace omen in panbanda/omen. Commands read from the repo's manifest — yesterday.

Slash commands (1)

• /omen-reporting:generate-report

Subagents (14)

• churn-analyst

  Analyzes code churn patterns to identify unstable areas that predict defects.

• components-analyst

  Analyzes per-component health trends (complexity, duplication, coupling, etc.).

• duplicates-analyst

  Analyzes code clones to identify duplication that causes maintenance burden and bugs.

• flags-analyst

  Analyzes feature flags to identify stale flags and cleanup opportunities.

• graph-analyst

  Analyzes the dependency graph to identify structural risks like high fan-out, central nodes, and import cycles.

• hotspot-analyst

  Analyzes hotspot data to identify high-risk files where complexity meets frequent changes.

• ownership-analyst

  Analyzes code ownership patterns to identify bus factor risks and knowledge silos.

• satd-analyst

  Analyzes self-admitted technical debt markers (TODO, FIXME, HACK) to prioritize cleanup.

• smells-analyst

  Analyzes architectural smells to identify structural issues like cyclic dependencies, hub modules, and instability.

• stubs-analyst

  Analyzes incomplete code (stubs) to surface half-finished work - not-implemented markers, placeholder comments, and empty function bodies.

• summary-analyst

  Synthesizes all analysis insights into executive summary and prioritized recommendations.

• tdg-analyst

  Analyzes Technical Debt Gradient scores to identify files with compounding debt across multiple dimensions.

• temporal-analyst

  Analyzes temporal coupling to identify files with hidden dependencies that change together.

• trends-analyst

  Analyzes health score trends over time to identify trajectory and inflection points.