review-deep

Generate candidate Reviewer evidence and validate code changes directly.

1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/alexandersumer/config --skill review-deep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-deep
Source: https://github.com/alexandersumer/config/tree/main/.agents/skills/review-deep
Command: npx skills add https://github.com/alexandersumer/config --skill review-deep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of conducting heavy-weight code reviews by generating candidate Reviewer evidence and validating changes directly by the agent.

Core Features & Use Cases

  • Automated Review Generation: Generates candidate evidence for Reviewers to review code changes.
  • Direct Validation: Validates changes directly, without delegation to subagents or recursive chains.
  • Use Case: When you need a deep, thorough review of a pull request or set of code changes, use this Skill to ensure comprehensive coverage of logic, security, and conventions.

Quick Start

Run the 'review-deep' skill on your set of code changes to automatically generate a review report.

Frequently Asked Questions about review-deep

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

FAQPage Schema
How do I automate a thorough code review for a pull request?

Automated code review generates candidate Reviewer evidence for fresh-context code changes and validates them directly. It provides comprehensive coverage of logic, security, and conventions without delegating to subagents.

How does fresh-context code review validation work?

Fresh-context code review validation works by generating candidate Reviewer evidence and validating changes directly by the agent. It avoids subagent delegation or recursive chains to perform heavy-weight validation of PRs and branches.

Does this code review automation rely on subagent delegation?

No, this code review automation does not rely on subagent delegation. It validates code changes directly by the agent, requiring direct invocation of Reviewer agents and thorough validation of outputs for heavy-weight reviews.

What is the best way to validate code changes across branches?

The best way to validate code changes across branches is using a heavy-weight review Skill that generates candidate Reviewer evidence. It directly validates logic, security, and conventions without recursive delegation.

When do I need heavy-weight code review automation?

You need heavy-weight code review automation when conducting thorough reviews of PRs, diffs, branches, and code changes. It ensures comprehensive validation of logic, security, and conventions by generating candidate Reviewer evidence.