code-review

Reviews implementation changes with parallel adversarial agents across correctness, performance, API, tests, and docs.

2|1|Updated May 11, 2019
One-click install
npx skills add https://github.com/guitarrapc/dotfiles-win --skill code-review-guitarrapc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/guitarrapc/dotfiles-win/tree/main/HOME/.agents/skills/code-review
Command: npx skills add https://github.com/guitarrapc/dotfiles-win --skill code-review-guitarrapc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss subtle defects because a single reviewer cannot cover correctness, performance, API usability, test coverage, and documentation consistency at once, and unverified findings waste time on false positives. ## Core Features & Use Cases - Parallel Multi-Lens Review: Runs independent reviewer agents concurrently across five lenses: correctness, performance, API usability, test coverage, and spec/doc synchronization. - Adversarial Claim Verification: Every shortlisted finding is challenged by three independent skeptical verifiers; claims refuted by at least two votes are removed before reporting. - Iterative Fix Loop: Validated findings are demonstrated with failing tests, fixed minimally, and the loop restarts until a round produces no surviving findings, followed by full test suite and benchmark checks. - Use Case: After finishing a bug fix in a C# service, invoke this Skill to have agents trace classification branches for false positives, check hot-path allocations, verify negative test coverage, and confirm docs match the new behavior before requesting external review. ## Quick Start Ask the AI to review the implementation changes in the current diff using the adversarial code review workflow before submitting for external review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I run an adversarial code review on my implementation changes?

Invoke the review after completing any implementation, modification, or bug fix. The workflow launches parallel reviewer agents across five lenses, verifies each finding with three skeptical verifiers, applies validated fixes, and repeats until no findings survive.

What does a multi-agent code review check that a single reviewer misses?

Independent agents cover correctness, performance, API usability, test coverage, and spec/doc synchronization concurrently without seeing each other's conclusions. This separation surfaces false positives in classification logic, hot-path allocations, and doc drift that one pass typically overlooks.

How are false positive findings filtered out before reporting?

Each shortlisted claim is given to three independent verification agents instructed to refute it with concrete counterevidence. A claim is removed only when at least two of three vote REFUTED; uncertainty or missing evidence never counts as refutation.

Does this review workflow support C# and .NET projects?

Yes. For C#/.NET changes it applies the dotnet-best-practices skill during investigation, and additionally uses dotnet-micro-optimization for performance-sensitive changes or known hot functions.

What test coverage is required for security-sensitive code?

Security-sensitive code, meaning anything enforcing access control, validating credentials, handling secrets, or preventing injection, must have negative tests greater than or equal to positive tests. Bug fixes also require a regression test that would catch re-introduction.

When does the review loop finish?

The loop ends when a full investigation round produces no validated findings. Completion then requires running the full test suite, checking benchmarks against the project regression threshold or a default of +10% latency and memory, and updating docs for any behavior changes.