review-local-changes

Review local unpushed changes and branch differences for critical issues.

3|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/otomatty/zedi --skill review-local-changes-otomatty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-local-changes
Source: https://github.com/otomatty/zedi/tree/main/.cursor/skills/review-local-changes
Command: npx skills add https://github.com/otomatty/zedi --skill review-local-changes-otomatty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing your local code changes or the differences between branches, ensuring code quality and catching potential issues before they are merged.

Core Features & Use Cases

  • Comprehensive Review: Analyzes your code for critical errors, warnings, and stylistic issues.
  • Contextual Analysis: Includes related files like tests and calling code in its review.
  • Branch Comparison: Identifies differences between your current branch and a target branch (e.g., develop or main).
  • Use Case: Before pushing your feature branch, run this Skill to get an AI-driven review that checks for security vulnerabilities, linting errors, and potential bugs, providing a detailed markdown report.

Quick Start

Review my current local changes and provide a detailed markdown report.

Frequently Asked Questions about review-local-changes

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

FAQPage Schema
How do I run an AI code review on my local Git diff before pushing?

AI code review analyzes unpushed local Git changes or branch differences to identify critical issues, warnings, and suggestions. It evaluates static analysis results, test file relevance, and calling code patterns to generate a comprehensive markdown report ensuring code quality and safety.

Can I compare my current branch against the main branch for potential bugs?

Yes, you can compare your current branch against a target branch like main or develop. The review identifies branch differences and analyzes the modified code for security vulnerabilities, linting errors, and potential bugs before merging.

Does the code review include related test files in its analysis?

Yes, the code review includes related test files and calling code patterns in its contextual analysis. By examining related files alongside your changes, it provides a comprehensive assessment of how modifications impact overall codebase safety and quality.

What is the best way to automate static analysis and linting checks for unpushed changes?

Automating static analysis and linting checks for unpushed changes is best handled by running an AI-driven code review before pushing. It analyzes your local diff for critical errors, warnings, and stylistic issues, delivering a detailed markdown report.

What format does the AI code review report use for output?

The AI code review report outputs in markdown format. This detailed document categorizes findings into critical issues, warnings, and informational suggestions, ensuring code quality and safety before you merge your branch.