code-reviewer

Inspect git diff and staged changes for logical conflicts and errors.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Ting-s515/skills --skill code-reviewer-ting-s515
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/Ting-s515/skills/tree/main/code-reviewer
Command: npx skills add https://github.com/Ting-s515/skills --skill code-reviewer-ting-s515

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams perform thorough pre-commit code reviews by systematically checking for logical conflicts, potential issues, and adherence to best practices before merging changes.

Core Features & Use Cases

  • Step-by-step diff evaluation using git diff and git diff --staged to capture both unstaged and staged changes.
  • Focus areas include logic correctness, edge-case handling, error propagation, and coding style alignment.
  • Use Case: during a feature review, apply this Skill to surface defects, improve readability, and reduce risk before pull requests.

Quick Start

Review the latest changes with this skill to generate a structured pre-commit code review.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review a git diff for potential logical conflicts before merging?

To review a git diff for logical conflicts, inspect staged and unstaged changes across a feature branch to identify potential errors, highlight risks, and enforce coding style adherence before merging.

What is the best way to enforce best practices during a pre-commit code review?

The best way to enforce best practices during a pre-commit code review is to systematically evaluate git diff output to surface defects, check edge-case handling, and verify error propagation before creating a pull request.

How does a pre-merge code review process handle state updates and coding style issues?

A pre-merge code review handles state updates and coding style issues by inspecting git diff --staged output, systematically highlighting missing state updates and style alignment deviations to reduce risk before merging.

Can I use a structured review process to improve readability and reduce risk in my feature branch?

Yes, you can use a structured review process to improve readability and reduce risk by applying step-by-step diff evaluation to your feature branch, focusing on logic correctness and edge-case handling before issuing pull requests.

Why does error propagation matter when inspecting a git diff for code changes?

Error propagation matters when inspecting a git diff because unhandled errors can introduce logical conflicts and defects into the main branch, making systematic checks for error handling essential before merging code changes.