complete-project-scope-code-review

Orchestrates parallel expert lanes to review an entire codebase and deliver verified findings, plans, and merges.

2|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Arasz/ai-badger --skill complete-project-scope-code-review-arasz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: complete-project-scope-code-review
Source: https://github.com/Arasz/ai-badger/tree/main/features/common/skills/complete-project-scope-code-review
Command: npx skills add https://github.com/Arasz/ai-badger --skill complete-project-scope-code-review-arasz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing a whole project — not just a diff — usually produces shallow, unverified findings that fall apart when someone tries to act on them. This Skill runs a full review campaign: measured ground truth, parallel expert lanes, adversarial falsification of the findings, severity calibration against production reality, a reviewed implementation plan, waved execution in isolated worktrees, and a join review on every merge. ## Core Features & Use Cases - Ground-truth baseline: Runs the project's build, test, and lint commands and verifies every claim at path:line before dispatching any reviewer. - Parallel expert lanes with evidence grades: Derives a lane roster from the repository's own stacks and directories, with a strict finding contract (MEASURED / READ / INFERRED / UNVERIFIED) and explicit permission to refute the brief. - Adversarial verification and severity calibration: An independent pass tries to falsify the record, and findings are checked against the live system so dormant defects are not treated as hotfixes. - Planned, gated implementation: Findings become work packages with gates that have been watched fail, executed in waves with a join review on every merge. - Use Case: Before a major release, ask for a full audit of the repository; the Skill returns a graded findings record, a reviewed plan, and merged fixes with decision records. ## Quick Start Ask the agent to run a complete project-scope code review of this repository and produce a graded findings record with an implementation plan.

Frequently Asked Questions about complete-project-scope-code-review

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

FAQPage Schema
How do I review an entire codebase instead of a single pull request?

Run a project-scope review campaign: measure a build/test/lint baseline at a named base commit, dispatch parallel read-only expert lanes derived from the repository's stacks, integrate their graded findings, then verify them adversarially before planning any fixes.

What is the difference between a project-scope review and a diff review?

A diff review judges one change against its base, while a project-scope review treats the whole codebase as the target and produces a graded findings record, a reviewed plan, and merged fixes. Use diff-scoped review skills for single PRs.

How does the review verify that findings are actually true?

Every finding carries a grade (MEASURED, READ, INFERRED, or UNVERIFIED) with path:line evidence, and an independent adversarial pass re-derives load-bearing claims and re-runs measured ones. Refuted or corrected claims are published in the record.

Can this review workflow work with Claude, .NET, and GitHub projects?

Yes, config-gated extensions bind the base workflow to specific environments. The Claude extension assigns lanes to model tiers, the dotnet extension covers .NET-specific traps like Dapper parameter drops, and the GitHub extension manages the campaign branch and PR.

When should I not use a full project-scope code review?

Do not use it for judging a single diff or PR, auditing one design document's gates, or answering one research question. Those cases belong to narrower skills like diff review checklists, design gate audits, or evidence-first research.