understand-diff

Included with Lifetime

$97 forever

Run a short active-recall dialogue that helps the user understand their current unstaged code changes. Use when the user wants to understand, review, quiz themselves on, or explain a local diff before accepting, committing, merging, or shipping it.

Code Review

What this skill does

# Understand Diff

Help the user understand their current unstaged changes with the least friction possible. The goal is active recall, not exhaustive review, grading, or commit approval.

## Workflow

1. Inspect the unstaged diff with `git diff`.
2. If there are no unstaged changes, ask the user what branch or commit range they want to compare.
3. Read surrounding code only when the diff alone is not enough to understand behavior, data flow, tests, or risk.
4. Identify the highest-leverage thing the user should be able to explain.
5. Ask one open-ended question immediately.
6. Wait for the user's answer.
7. Give brief feedback, then either ask one useful follow-up or finish with a short summary.

## Question Style

- Ask the fewest questions that can produce real understanding.
- Prefer behavior, intent, data flow, risk, and tests over line-by-line trivia.
- Use open-ended prompts that require the user to explain in their own words.
- Do not use multiple choice unless the user is stuck and needs scaffolding.
- Do not announce a quiz plan, concept list, file count, or full diff summary before the first question.
- Do not reveal the answer before the user has attempted an explanation.

## Feedback

After each answer:

- say what the user got right
- point out the most important missing or incorrect part
- ask a sharper follow-up only if it would materially improve understanding
- give a small hint before giving a full explanation when the user is stuck

## Completion

Finish as soon as the user has shown enough understanding of the main changed behavior, reason for the change, and relevant risk or test implication.

End with a concise summary of:

- what the user demonstrated
- any important unresolved risk
- any useful verification step

Do not say the change is ready to commit. Say only what the user demonstrated about their understanding.

Files: 1

Size: 2.1 KB

Complexity: 11/100

Category: Code Review

Source: https://github.com/sidkh/skills/tree/main/understand-diff

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts