review-scope

Audit repository changes and file sets to produce a findings report.

9|1|Updated Jan 8, 2026

Search Tags:#audit #review #code-review #diffs #uncommitted-changes #findings #hotspot

Ready to run

npx skills add https://github.com/conn-castle/agent-layer --skill review-scope-conn-castle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-scope
Source: https://github.com/conn-castle/agent-layer/tree/main/internal/templates/skills/review-scope
Command: npx skills add https://github.com/conn-castle/agent-layer --skill review-scope-conn-castle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines targeted reviews of code changes and repo slices to surface correctness, architecture, and maintainability issues before deployment.

Core Features & Use Cases

Correctness review of explicit plan artifacts or diffs
Proactive hotspot audits to identify high-risk areas
Precise target selection for unstaged changes, staged changes, or specific file sets
Multi-agent review lenses (Correctness, Architecture, Quality, Maintainer) to surface diverse risks
Evidence-backed findings with an auditable report

Quick Start

Run the review-scope skill against the current repository to generate a findings report

Frequently Asked Questions about review-scope

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

FAQPage Schema

How do I review uncommitted changes for correctness and architecture issues?▼

You can review uncommitted changes by running an audit against staged or unstaged diffs to produce a structured findings report. It applies Correctness, Architecture, Quality, and Maintainer review lenses to surface diverse risks.

How do I conduct a proactive hotspot audit on specific file sets?▼

Proactive hotspot audits target specific file sets to surface correctness and maintainability issues. The audit identifies high-risk areas and outputs an evidence-backed findings report suitable for per-repo review.

What is the best way to generate an evidence-backed codebase review report?▼

Generating an evidence-backed codebase review report requires auditing repository changes or targeted file sets. It evaluates diffs and explicit plan artifacts to produce structured findings with auditable conclusions.

Can I review explicit plan artifacts against actual code diffs?▼

Yes, you can apply a correctness review to explicit plan artifacts and code diffs. The audit evaluates these targets to surface discrepancies and issues before deployment.

Does the code review process support both staged and unstaged changes?▼

The code review process supports precise target selection for both staged and unstaged changes. It audits these repository changes to identify correctness, architecture, and maintainability issues.