skills.rest
nesnilnehc
nesnilnehcCOMMUNITY
Explore all skills by this author →
GitHub

review-diff

Analyze git diffs across five dimensions with precise location references.

7|3|Updated Jan 23, 2026
Search Tags:#git#diff#scope#code-review#locations#findings
One-click install
npx skills add https://github.com/nesnilnehc/ai-cortex --skill review-diff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-diff
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/review-diff
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill review-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze the current git diff (staged, unstaged, and included untracked files) to surface scope-based findings.

Core Features & Use Cases

  • Evaluates changes confined to the diff, including newly added untracked files, for focused reviews.
  • Produces findings across five dimensions: intent/impact, regression, compatibility, side effects, and observability.
  • Includes precise location references (file:line or @@ blocks) and actionable recommendations to guide reviewers and consumers.

Quick Start

Provide the current git diff and any new untracked files to generate scope findings.

Frequently Asked Questions about review-diff

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

FAQPage Schema
How do I review a git diff for code changes scoped only to my current modifications?▼

Review a git diff by evaluating changes across five dimensions: intent/impact, regression, compatibility, side effects, and observability. This scope-based analysis produces actionable recommendations with precise file:line or @@ block references for safe, focused code reviews.

What's the best way to find regression and compatibility issues in a git diff?▼

Surface regression and compatibility issues in a git diff by applying a scope-based analysis across five dimensions. This approach evaluates only changed files and includes newly added untracked files, producing actionable recommendations anchored to exact file:line locations.

How do I get actionable code review findings with precise file and line references?▼

Generate actionable code review findings with precise references by analyzing the current git diff across five dimensions: intent/impact, regression, compatibility, side effects, and observability. All findings are anchored to exact file:line or @@ block locations for aggregation.

Does scope-based diff review include untracked files in the code analysis?▼

Yes, scope-based diff review includes untracked files in the code analysis. It evaluates changes confined to the diff, including newly added untracked files, to produce focused findings across five dimensions with precise file:line or @@ block references.

When do I need to analyze side effects and observability in a code diff?▼

Analyze side effects and observability in a code diff when evaluating changes across five dimensions for scope-based findings. This ensures the review captures unintended consequences and monitoring gaps, producing actionable recommendations anchored to exact file:line locations.

Related Skills

Explore More Software Engineering Skills→
jie-mengjie-meng
1

code-review-staged

Review staged git changes and generate a six-section code review with a commit message.

Community
Advanced
olioskarolioskar

plan

Convert comb review findings into executable fix instructions with citations.

Community
Advanced
nanorepublicananorepublica
61

Global Tech Stack

Validate code against centralized global tech stack standards.

Community
Basic
shouqitaoshouqitao

lybtzyzs-mvp-compliance

Scan code for disallowed technologies and over-engineered patterns.

Community
Intermediate