skills.rest
nrdxp
nrdxpCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-review

Reviews git history and commits for change coherence against a stated purpose.

10|2|Updated Jan 24, 2026
Search Tags:#git#diff analysis#code review#version control#commit history#git log#change coherence
One-click install
npx skills add https://github.com/nrdxp/predicate --skill git-review-nrdxp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-review
Source: https://github.com/nrdxp/predicate/tree/main/skills/git-review
Command: npx skills add https://github.com/nrdxp/predicate --skill git-review-nrdxp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing git history without a clear goal leads to aimless browsing and missed issues. This Skill enforces a purpose-driven review workflow that traces changes, checks commit coherence, and surfaces scope drift, undocumented breaking changes, and non-atomic commits. ## Core Features & Use Cases - Purpose-First Review: Requires declaring what you are investigating before touching history, keeping the review focused. - Three Review Modes: SUMMARY for scanning recent history, SEARCH for finding relevant commits by message, file, or code change, and EXPAND for examining specific commits in detail. - Coherence Checklist: Assesses scope alignment, API consistency, breaking changes, debt tracking, and commit atomicity, then outputs a structured report with findings, concerns, and recommendations. - Use Case: Before modifying an authentication module, use this Skill to trace how it evolved, find where the API contract changed, and verify each change was justified and documented. ## Quick Start Ask the agent to run a git review tracing how the authentication module evolved over the last month and flag any commits whose changes do not match their messages.

Frequently Asked Questions about git-review

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

FAQPage Schema
How do I review git history for a specific file or change?▼

Use git log --all --oneline -- path/to/file to see a file's history, git log --grep to search commit messages, or git log -S to find commits that changed specific code. Then use git show on relevant hashes to examine details.

How to check if commits match their commit messages?▼

Examine each commit with git show and compare the diff against the message using a coherence checklist: scope alignment, API consistency, documented breaking changes, and atomicity. Commits with 'and' in the message or unexplained scope changes are red flags.

What makes a good git commit for code review?▼

A good commit is atomic with a single logical change, has a message matching its actual scope, documents any breaking changes or technical debt, and is independently reviewable without external context.

When should I not use git history review for debugging?▼

History review is less effective when the bug was introduced outside version control, when history was rewritten or squashed losing detail, or when the issue stems from environment or dependency changes not captured in commits.

Can git review detect breaking API changes?▼

Yes, by searching history for commits touching API-related files and examining their diffs, you can identify breaking changes. The review checks whether such changes were documented and justified in the commit message.

Related Skills

Explore More Software Engineering Skills→
stacklokstacklok
2.0k

commit-message

Generates commit messages from staged files for common use cases.

Official
Intermediate
withzombieswithzombies
80

fixing-bugs

Automate bug fixing from issue creation through regression testing and closure.

Community
Advanced
rogerzntsrogerznts
1

tea-commit

Stages pending changes and creates Conventional Commits messages from git diffs.

Community
Basic
entireioentireio
208

what-happened

Trace git blame provenance for code blocks with checkpoint-backed explanations.

Official
Advanced