code-review

Organize git branch changes into Atomic Views for structured code reviews.

Updated Mar 17, 2017
One-click install
npx skills add https://github.com/dfmonaco/dotfiles --skill code-review-dfmonaco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/dfmonaco/dotfiles/tree/main/archive/agents-skills/code-review
Command: npx skills add https://github.com/dfmonaco/dotfiles --skill code-review-dfmonaco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze a git branch (or PR) relative to a base and produce a structured review organized as Atomic Views -- single-purpose change groups presented in narrative (oldest-to-newest) order.

Core Features & Use Cases

  • Atomic Views ensure each issue has a single explicit WHY and a bounded set of files.
  • Narrative order preserves history by presenting changes from oldest to newest.
  • Provides actionable findings with rationale, severity, and suggested directions.
  • Useful for pre-merge reviews, quality passes, and security/code quality audits.

Quick Start

Provide a structured code review for a git branch or pull request using Atomic Views in oldest-to-newest narrative order.

Frequently Asked Questions about code-review

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

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

You can automate a structured code review by organizing branch changes into Atomic Views, which are single-purpose change groups presented in oldest-to-newest narrative order to provide clear, actionable assessments.

What are atomic views in a code review?

Atomic views in a code review are single-purpose change groups that ensure each identified issue has a single explicit WHY and a bounded set of files, preserving history by presenting changes in oldest-to-newest narrative order.

Can I use this for pre-merge checks and architecture audits?

Yes, this approach applies to pre-merge checks, architecture audits, and quality or security reviews across multiple commits by analyzing a git branch relative to a base and producing structured findings with rationale and severity.

What is the best way to review multiple commits in a branch?

The best way to review multiple commits in a branch is to organize changes into atomic views ordered oldest-to-newest, which preserves commit history and provides actionable findings with suggested directions for improvements.

Do I need to define a base branch to review a pull request?

Yes, you need a base branch for comparison. The review process analyzes a git branch or pull request relative to this base to produce a structured assessment organized as single-purpose Atomic Views.