skills.rest
gustavofsantos
gustavofsantosCOMMUNITY
Explore all skills by this author →
Website𝕏@ggggsantosGitHub

review

Automates two-phase code review guidance for evaluating branch diffs, PRs, and single-file changes.

Updated Mar 12, 2019
Search Tags:#architecture#safety#best-practices#quality-assurance#code-review#phase-1#depth-review
One-click install
npx skills add https://github.com/gustavofsantos/dot-files --skill review-gustavofsantos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/gustavofsantos/dot-files/tree/main/skills/review
Command: npx skills add https://github.com/gustavofsantos/dot-files --skill review-gustavofsantos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Two-phase code review framework that ensures safety assessment and architectural depth for code changes, reducing risk before merging.

Core Features & Use Cases

  • Phase 1: Scope and safety evaluation for tests, risk signals, and change scope
  • Phase 2: Depth review focusing on the core logic and architectural quality
  • Works on branch diffs, single files, or usage patterns and replaces both review-branch and use-reviewer workflows
  • Produces a structured verdict and actionable feedback for developers and reviewers

Quick Start

Provide a diff or describe the code change; follow the two-phase review prompts to generate a structured assessment.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a structured two-phase code review on a pull request?▼

A structured code review automates a two-phase evaluation for pull requests, checking test confidence and safety in Phase 1, then analyzing core logic depth in Phase 2 to produce a final verdict.

What is a safety-first code review and how does it evaluate risk?▼

A safety-first code review evaluates risk by assessing test confidence, scope discipline, and risk signals in Phase 1 before proceeding to architectural depth, ensuring changes are safe to merge.

Can I use this code review workflow for single-file changes and branch diffs?▼

Yes, the code review workflow applies to single-file changes, branch diffs, and pull requests, replacing separate review workflows with a unified two-phase assessment process.

How do I automate architecture-focused quality assurance assessments for code changes?▼

Automated architecture-focused assessments evaluate core logic and architectural quality during Phase 2 of the review, generating actionable feedback and a structured verdict for developers.

What is the best way to scale code reviews across multiple branch diffs?▼

Scaling code reviews relies on a structured two-phase framework that standardizes scope discipline and safety evaluations, generating consistent architectural assessments across all diffs.

When should I not use a two-phase code review workflow?▼

A two-phase code review workflow may be unnecessary for trivial changes that do not impact architecture or safety, as the structured Phase 1 and Phase 2 assessments target meaningful risk reduction.

Related Skills

Explore More Software Engineering Skills→
hamzaPixlhamzaPixl
2

cross-review

Run dual-model code reviews on pull request diffs and match findings by file and line.

Community
Advanced
MuhamadAnangMuhamadAnang

code-review-expert

Analyzes git diffs for SOLID violations, security risks, and performance issues.

Community
Advanced
yocxy2yocxy2

health

Calculate a weighted code quality score from linter, test, and static analysis results.

Community
Advanced
alexandervashurinalexandervashurin

codex

Run diff-based code reviews, adversarial challenges, and consult prompts via Codex CLI.

Community
Advanced