combined-review

Plugin combined-review from marketplace awac-ai-agent-plugins in IvanLutsenko/awac-ai-agent-plugins. Commands read from the repo's manifest — 2 days ago.

Skills (8)

• combined-review-code-reviewer

  Reviews code changes for repo-policy compliance (CLAUDE.md / AGENTS.md), bugs, logic errors, and code quality. Reads full files (not just diff) for context. Use when reviewing any code changes — PR, branch diff, or uncommitted work.

• combined-review-git-historian

  Analyzes git blame and history for changed files. Detects reverted fixes, frequently broken code, parallel work conflicts, and lost changes. Use when reviewing code changes that touch critical or frequently modified files.

• combined-review-security-reviewer

  Audits code changes for security defects — secrets in source, injection, insecure storage and transport, broken authn/authz, unsafe deserialization, unvalidated input crossing a trust boundary. Stack-agnostic: derives the platform's idioms from the repo. Runs on every review, like the other four age

• combined-review-silent-failure-hunter

  Audits error handling in code changes. Finds silent failures, empty catch blocks, broad exception catching, unjustified fallbacks, and missing error feedback. Zero tolerance for swallowed errors.

• combined-review-test-analyzer

  Analyzes test coverage quality for code changes. Focuses on behavioral coverage, identifies critical gaps in error paths and edge cases. Reports only gaps with criticality >= 7/10.

• combined-review-rereview

  Re-review a GitHub PR or GitLab MR: check whether your own unresolved threads were actually fixed in the new revision, then resolve and approve. Use when the user invokes /rereview.

• combined-review-review-config

  Set up combined-review: language, subagent model, CodeRabbit. Writes a config that survives plugin updates. Use when the user invokes /review-config.

• combined-review-review

  Combined code review: multi-agent analysis + CodeRabbit. Supports GitHub PR, GitLab MR, branch diff, uncommitted changes. Use when the user invokes /review.

Slash commands (3)

• /combined-review:rereview

  Re-review a GitHub PR or GitLab MR: check whether your own unresolved threads were actually fixed in the new revision, then resolve and approve.

• /combined-review:review-config

  Set up combined-review: language, subagent model, CodeRabbit. Writes a config that survives plugin updates.

• /combined-review:review

  Combined code review: multi-agent analysis + CodeRabbit. Supports GitHub PR, GitLab MR, branch diff, uncommitted changes.

Subagents (5)

• code-reviewer

  Reviews code changes for repo-policy compliance (CLAUDE.md / AGENTS.md), bugs, logic errors, and code quality. Reads full files (not just diff) for context. Use when reviewing any code changes — PR, branch diff, or uncommitted work.\n\nExamples:\n<example>\nContext: User wants a code review of their

• git-historian

  Analyzes git blame and history for changed files. Detects reverted fixes, frequently broken code, parallel work conflicts, and lost changes. Use when reviewing code changes that touch critical or frequently modified files.\n\nExamples:\n<example>\nContext: Reviewing changes to a file with complex hi

• security-reviewer

  Audits code changes for security defects — secrets in source, injection, insecure storage and transport, broken authn/authz, unsafe deserialization, unvalidated input crossing a trust boundary. Stack-agnostic: derives the platform's idioms from the repo. Runs on every review, like the other four age

• silent-failure-hunter

  Audits error handling in code changes. Finds silent failures, empty catch blocks, broad exception catching, unjustified fallbacks, and missing error feedback. Zero tolerance for swallowed errors.\n\nExamples:\n<example>\nContext: Reviewing code with try-catch blocks\nuser: \"Check the error handling

• test-analyzer

  Analyzes test coverage quality for code changes. Focuses on behavioral coverage, identifies critical gaps in error paths and edge cases. Reports only gaps with criticality >= 7/10.\n\nExamples:\n<example>\nContext: Reviewing code changes with business logic\nuser: \"Are there enough tests for these

Similar plugins