code-review-and-commit

Review uncommitted Git changes and generate an atomic commit plan.

Updated Feb 8, 2026

Search Tags:#automation #git #workflow #commit #quality-assurance #code-review #version-control

Ready to run

npx skills add https://github.com/abpai/skills --skill code-review-and-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-and-commit
Source: https://github.com/abpai/skills/tree/main/code-review-and-commit
Command: npx skills add https://github.com/abpai/skills --skill code-review-and-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review uncommitted Git changes for correctness, quality, and project convention alignment, then apply fixes and prepare a safe, atomic commit plan.

Core Features & Use Cases

Inspect current change scope (unstaged and staged changes) for correctness and maintainability.
Propose targeted fixes, enforce repository conventions, and build an atomic commit plan.
Provide an approval gate before performing git add/git commit to ensure safe, auditable history.

Quick Start

Use this skill to review your working tree and generate a plan to commit changes in coherent steps.

Frequently Asked Questions about code-review-and-commit

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

FAQPage Schema

How do I review uncommitted Git changes before committing?▼

Splitting changes into conventional commits involves inspecting unstaged and staged diffs to group related modifications. This process builds an atomic commit plan, ensuring each commit represents a single logical change for better maintainability.

What is the best way to prepare a safe Git workflow for local development?▼

Preparing a safe Git workflow requires inspecting local working tree changes for correctness and convention alignment. It outputs a structured commit plan with an approval gate before executing git add or git commit, ensuring auditable history.

Can I enforce project conventions when reviewing unstaged code changes?▼

You can enforce project conventions by inspecting unstaged and staged changes for alignment. The review process proposes targeted fixes to maintain code quality and ensures modifications adhere to established repository standards before committing.

Does this code review process provide an approval gate before running git commit?▼

Yes, the code review process provides an explicit approval gate before performing git add and git commit. This ensures safe, auditable history by requiring user validation of the structured commit plan before any version control actions execute.

When should I not use automated code review for my Git workflow?▼

You should not use automated code review when dealing with changes that require subjective architectural decisions beyond convention alignment. It is designed for deterministic inspection of local diffs and generating safe commit plans, not deep semantic logic validation.