odin-review

Plugin odin-review from marketplace odin-marketplace in OutlineDriven/odin-claude-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (17)

• audit-project

  Use when the user says "audit my code", "find all the bugs", "review until clean", or "grill my changes". Not for remote, credential, or irreversible changes.

• ax-audit

  Use when asked to audit an agent or AI feature for agentic-experience quality (AX review, agent-native critique, trust question). Not for source or remote-system changes.

• blast-radius

  Use when asked to determine what a change could break before it ships. Not for remote, credential, publish, deploy, or irreversible changes.

• complexity-grill

  Use when a user wants to identify the true sources of complexity qualitatively before counting metrics. Not for source or remote mutation.

• dx-audit

  Use when auditing the developer-facing surface of a CLI, SDK, library, or package: API contracts, errors, public types, onboarding, and config.

• feedback-pattern-sweep

  Use when recent resolved feedback may reveal a broader recurring defect pattern across the project surface. Not for source-level feedback collection: use feedback-sweep.

• interrogate

  Use when asked to "interrogate" or run an adversarial multi-model review of a supplied code artifact. Not for tasks that require source or remote-system changes.

• no-hide

  Use when the user asks to detect clever-concealment patterns that obscure real code structure. Not for refactoring the concealment away: use unleak-abstraction.

• perspective-complete-review

  Use when one named review viewpoint must run fix cycles until a fresh reviewer finds nothing. Not for multi-viewpoint review or remote, credential, publish, deploy, or irreversible changes.

• pr-impact-quiz

  Use when the user invokes this skill to generate targeted questions proving the author understands the change''s codebase effect. Not for reviewing the change: use review.

• review-speedread

  Use when a human asks for the change shape before reading a diff. Not for a full findings report: use review. For an interactive walk: use show-review.

• review

  Use when asked to review a pull request, examine code changes, find bugs, or audit a branch, in standard or depth mode. Not for an iterative review-and-fix loop: use audit-project.

• sarif-parsing

  Use when a user supplies existing SARIF to inspect, filter, aggregate, deduplicate, diff, convert, or gate findings. Not for running a scanner: use the relevant security-review skill.

• show-review

  Use when the user wants a per-finding visual walk through a diff or PR. Not for written review reports: use review. Not for codebase tours: use show-me.

• spec-to-code-compliance

  Use when implementation must be checked against an authoritative specification, or during PR review for spec drift against checked-in specs. Not for spec updates: use spec-driven-implementation.

• validate-changes-match-specs

  Use when asked to compare implementation against repository specs, report mismatches, resolve by user decision, or check PR-review commitments. Not for general fact-checking: use verify-both-ways.

• visual-diff-review

  Use when asked to review a diff and produce a 7-section visual page. Not for interactive review walks or PR-specific review: use show-review.

Similar plugins