spicy-review

Plugin spicy-review from marketplace spicyclaude in d-mariano/spicyclaude. Commands read from the repo's manifest — 4 days ago.

Skills (2)

• code-review-light

  Fast single-pass code review of a diff. Use for a quick read-only review of a PR or the current branch — pulls the diff, runs one consolidated pass against the shared severity rubric, and prints a severity-tiered summary. No subagents, never posts. For deep multi-reviewer review use /spicy-review:re

• review-heavy

  Deep, risk-tiered multi-reviewer code review. Sizes the change, fans out to the right set of read-only reviewer subagents in parallel, cross-checks findings with a verification pass, then prints one severity-tiered report and verdict — and optionally posts it to the PR (inline + summary). Never appr

Subagents (10)

• code-quality

  Code-review reviewer focused on over-engineering and unnecessary complexity in a diff. Use during a code review to flag premature abstractions, single-use helpers, framework-level solutions to one-off problems, needless indirection, duplication, and dead code. Core question — does this complexity se

• deps

  Code-review reviewer for dependency hygiene when a diff adds or changes dependencies. Use during a code review (Tier-2) to flag heavyweight deps for trivial needs, unmaintained/risky packages, license issues, duplicates of existing capability, and loose version pinning. Read-only; never posts.

• documentation

  Code-review reviewer for comment and documentation hygiene in a diff. Use during a code review to flag comment rot, outdated/misleading comments, over-documentation, comments on self-explanatory code, and CLAUDE.md bloat. Wants docs that describe the current state concisely, not history or narration

• mental-alignment

  Code-review reviewer that checks whether a diff actually does what it claims. Use during a code review to compare stated intent (the PR description plus the Jira ticket's description and acceptance criteria) against the real changes, flagging unimplemented requirements, scope creep, and behavior tha

• observability

  Code-review reviewer for logging/metrics/tracing signal on a diff. Use during a code review (Tier-2) to flag silently-swallowed errors, missing signal on important new failure paths, and the inverse — noisy or excessive logging the change introduces. Read-only; never posts.

• performance

  Code-review reviewer for concrete performance regressions in a diff. Use during a code review (Tier-2) to flag N+1 queries, accidental O(n^2), unbounded memory growth, and blocking work on a hot path that the change introduces. Measurable-impact only, never speculative micro-optimization. Read-only;

• security

  Code-review reviewer for concretely exploitable security flaws in a diff. Use during a code review to check changed code for injection, authz/authn bypass, hardcoded secrets, insecure crypto, sensitive data in logs/errors, and missing validation at trust boundaries. Exploitable-or-concretely-dangero

• simplification

  Code-review reviewer for concrete reuse and dead-code opportunities in a diff. Use during a code review (Tier-2) to flag reimplementations of something the project/stdlib already provides, dead code the change adds, and clearly simpler equivalents. Distinct from code-quality (which owns over-enginee

• tests

  Code-review reviewer for test adequacy on a diff. Use during a code review (Tier-2) to flag changed behavior with no test covering it, tests that assert nothing or can't fail, and brittle patterns the change introduces. Read-only; never posts.

• verification

  Cross-check reviewer that re-validates candidate code-review findings before they are surfaced or posted. Use after the other reviewers to independently confirm each finding against the actual code, dropping false positives and pre-existing issues and fixing mis-scored severity/confidence. Precision