omen
01Plugin Claude Code
Plugin marketplace listing 2 plugins: omen-development, omen-reporting.
Plugin Claude Code
Plugin marketplace listing 2 plugins: omen-development, omen-reporting.
Instructions file
Instructions for panbanda/omen, covering claude.md, build and development commands, setup git hooks (run once after clone), format code and run linter.
Skill Claude CodeCodex
Analyze blast radius before changing specific files. Use before refactoring core components, making breaking API changes, or modifying shared code to identify affected files and stakeholders.
Skill Claude CodeCodex
Audit module coupling, cohesion, hidden dependencies, and design smells. Use when conducting architecture reviews, evaluating design decisions, or identifying structural tech debt.
Skill Claude CodeCodex
Identify stale feature flags and prioritize cleanup. Use when cleaning up flags after launches, during monthly hygiene reviews, or before major releases.
Skill Claude CodeCodex
Assess overall code quality.
Skill Claude CodeCodex
Get complexity and debt metrics before editing code.
Skill Claude CodeCodex
Locate likely bug locations in code.
Skill Claude CodeCodex
Focus code review on high-risk changes.
Skill Claude CodeCodex
Generate onboarding guide with key symbols, architecture overview, and subject matter experts. Use when joining a new project, onboarding teammates, or creating project documentation.
Skill Claude CodeCodex
Identify highest-ROI refactoring targets.
Skill Claude CodeCodex
Generate comprehensive tech debt assessment with quantified metrics and prioritized issues. Use for sprint planning, stakeholder reports, or justifying refactoring time allocation.
Skill Claude CodeCodex
Analyze a repository and generate an intelligent omen.toml with project-specific defaults. Use when starting Omen in a new project.
Skill Claude CodeCodex
Identify files and functions most needing test coverage based on risk, complexity, and churn. Use when prioritizing test writing or improving coverage strategically.
Skill Claude CodeCodex
Analyze repository health trends over time using historical git commits. Use for quarterly reports, release retrospectives, or tracking technical debt paydown progress.
Agent
Analyzes code churn patterns to identify unstable areas that predict defects.
Agent
Analyzes per-component health trends (complexity, duplication, coupling, etc.).
Agent
Analyzes code clones to identify duplication that causes maintenance burden and bugs.
Agent
Analyzes feature flags to identify stale flags and cleanup opportunities.
Agent
Analyzes the dependency graph to identify structural risks like high fan-out, central nodes, and import cycles.
Agent
Analyzes hotspot data to identify high-risk files where complexity meets frequent changes.
Agent
Analyzes code ownership patterns to identify bus factor risks and knowledge silos.
Agent
Analyzes self-admitted technical debt markers (TODO, FIXME, HACK) to prioritize cleanup.
Agent
Analyzes architectural smells to identify structural issues like cyclic dependencies, hub modules, and instability.