code-review

Review code diffs adversarially and triage findings into actionable categories.

3|1|Updated May 12, 2026
One-click install
npx skills add https://github.com/LumenWipe/lumenwipe --skill code-review-lumenwipe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/LumenWipe/lumenwipe/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/LumenWipe/lumenwipe --skill code-review-lumenwipe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify bugs, edge cases, specification violations, and acceptance gaps in code changes before they reach production, while reducing review noise through structured triage.

Core Features & Use Cases

  • Adversarial Review Layers: Coordinates Blind Hunter, Edge Case Hunter, and Acceptance Auditor reviews for independent perspectives.
  • Context-Aware Analysis: Reviews staged changes, working-tree changes, branches, commit ranges, or supplied diffs with optional story and specification context.
  • Structured Triage: Normalizes, deduplicates, and classifies findings as decision-needed, patch, defer, or dismiss.
  • Actionable Workflow: Presents findings, supports patch handling, records review results in story files, and synchronizes sprint status when applicable.
  • Use Case: Use this Skill to review a feature branch against main, detect failure paths and acceptance-criteria gaps, and produce prioritized fixes before merging.

Quick Start

Ask the code-review skill to review the current branch against main and assess the changes against the relevant story or specification.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate adversarial code review for pull requests?

You can review a feature branch against main by supplying the branch diff along with optional project specifications and acceptance criteria. The review runs parallel analysis layers and normalizes findings into prioritized, actionable patches.

What is the best way to check if code changes meet acceptance criteria?

Checking code changes against acceptance criteria involves auditing the diff for specification violations and functional gaps. An acceptance auditor layer evaluates the changes independently to identify missing requirements before production deployment.

Can I review staged changes and working-tree changes without a full branch diff?

Yes, code review supports staged changes, working-tree changes, and specific commit ranges. It constructs the required diff contextually and applies adversarial analysis to detect failure paths and specification violations without needing a full branch diff.

How does structured triage reduce noise in diff review findings?

Structured triage reduces diff review noise by normalizing and deduplicating discovered findings. It classifies issues into decision-needed, patch, defer, or dismiss categories so you can focus only on prioritized, actionable fixes.

Do I need project specifications to perform an adversarial diff review?

Project specifications are optional for adversarial diff review. While providing story files and acceptance criteria enhances context-aware analysis, the review can operate directly on supplied diffs to identify bugs and edge cases.