code-review-git-en

Analyze Git diffs for code quality and documentation drift.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ousiass/claude-config --skill code-review-git-en
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-git-en
Source: https://github.com/ousiass/claude-config/tree/main/skills/code-review-git-en
Command: npx skills add https://github.com/ousiass/claude-config --skill code-review-git-en

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of checking code quality and detecting documentation drift specifically within the changes introduced by a Git diff, making pre-commit reviews more efficient.

Core Features & Use Cases

  • Code Quality Analysis: Analyzes only the changed code for potential bugs, style violations, and architectural issues.
  • Documentation Drift Detection: Compares changes in code against changes in documentation within the same diff to ensure consistency.
  • Use Case: Before creating a Pull Request, use this Skill to perform a self-review on your branch's changes against origin/develop to catch issues early and ensure documentation is up-to-date with the code.

Quick Start

Run a code review on the current branch's changes compared to origin/develop.

Frequently Asked Questions about code-review-git-en

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

FAQPage Schema
How do I check code quality on a git diff before committing?

To check code quality on a git diff, you analyze changed files against a remote branch for potential bugs, style violations, and architectural issues. This process reviews only the modified code to catch problems before creating a pull request.

What is documentation drift detection in a git diff?

Documentation drift detection compares code changes against documentation updates within the same git diff scope to ensure consistency. It identifies mismatches where modified code lacks corresponding documentation changes.

Can I review changes against origin/develop before creating a pull request?

Yes, you can review your current branch's changes against origin/develop before creating a pull request. This self-review catches issues early and verifies documentation remains up-to-date with the modified code.

How does a code review report categorize findings?

A code review report categorizes findings into critical, important, suggestion, and minor levels. This classification helps prioritize recommended improvements by highlighting severe code quality and documentation issues.

Do I need CI/CD pipelines to run pre-commit quality checks?

No, you do not need CI/CD pipelines to run pre-commit quality checks. You can perform local self-reviews on your branch's changes against a remote branch directly before pushing, ensuring code quality and documentation consistency.