review

Analyze git diffs between the current branch and main to generate change summaries.

Updated May 25, 2025
One-click install
npx skills add https://github.com/temple-slope/dotfiles --skill review-temple-slope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/temple-slope/dotfiles/tree/main/dot_claude/skills/review
Command: npx skills add https://github.com/temple-slope/dotfiles --skill review-temple-slope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze diffs between the current branch and main to improve PR quality.

Core Features & Use Cases

  • Generate a concise change summary listing modified files, edited code blocks, and potential impact.
  • Support review scenarios for feature branches, hotfixes, and release candidates with clear context for reviewers.
  • Flag potential concerns like large refactors, sensitive changes, or unclear diffs to prompt further investigation.

Quick Start

Run the review workflow on the current branch to produce a succinct change summary for the upcoming PR.

Frequently Asked Questions about review

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

FAQPage Schema
How do I generate a concise change summary for a git pull request?

To generate a concise change summary for a pull request, analyze the git diff between your current feature branch and main. This lists modified files, edited code blocks, and potential impact to provide clear context for reviewers.

How do I review large refactors and sensitive changes in a git diff?

Reviewing large refactors and sensitive changes in a git diff involves analyzing the branch history to flag potential concerns. This prompts further investigation by highlighting unclear diffs and sensitive modifications for reviewers.

Can I use automated diff analysis for hotfixes and release candidates?

Yes, you can use automated diff analysis for hotfixes and release candidates. The workflow supports these review scenarios by generating succinct change summaries and highlighting potential issues across software projects.

What's the best way to improve PR quality before submitting a feature branch?

The best way to improve PR quality before submitting a feature branch is to analyze the diff against main. This highlights potential issues and generates a concise change summary to provide clear context for reviewers.

How does listing changed files from a branch diff help code review?

Listing changed files from a branch diff helps code review by generating a concise change summary. It identifies modified files and edited code blocks to flag potential concerns, prompting further investigation for reviewers.