commit-review

Reviews git commits across seven quality dimensions with evidence-backed conclusions.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/lldwb/lldwb-claude-skills --skill commit-review-lldwb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-review
Source: https://github.com/lldwb/lldwb-claude-skills/tree/main/skills/commit-review
Command: npx skills add https://github.com/lldwb/lldwb-claude-skills --skill commit-review-lldwb

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Reviewing a commit by eyeballing its diff often misses defects that only surface when you trace callers, contracts, and repository conventions. This Skill performs a structured, evidence-backed quality review of any specified revision (commit sha, branch, or tag) and delivers a clear binary verdict—issues found or no issues—without modifying any code. ## Core Features & Use Cases - Seven-dimension audit: Checks logic and boundaries, dependency impact, layering and coupling, contract change impact, deprecated API usage, style and repository convention consistency, and commit message compliance (including a dedicated release-commit checklist). - Evidence-traceable conclusions: Every finding cites a diff hunk, file:line, or command output, and is graded as critical, convention, or suggestion. - Beyond-the-diff exploration: Uses Grep/Glob/Read to trace call chains and full-repository references, with optional read-only subagents for large impact searches. - Use Case: After a teammate merges a pull request, ask the agent to review the merge commit; it fetches the commit data via the bundled script, inspects affected callers across the repo, and reports whether the commit introduced defects or violated conventions. ## Quick Start Use the commit-review skill to review commit abc1234 and tell me whether it introduced any problems.

Frequently Asked Questions about commit-review

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

FAQPage Schema
How do I review a git commit for quality issues?

Provide the commit sha, branch, or tag and the skill runs a script that writes the commit metadata and diff to disk, then checks seven dimensions including logic, dependency impact, and commit message format. It returns a binary conclusion of issues found or no issues, with each finding citing a diff line or file:line.

How to check if a commit broke other callers in the repository?

The review performs full-repository searches for every changed method signature, constant, enum, and config key to find all callers, not just the diff. For large search scopes it can dispatch read-only subagents that report caller lists with file:line references.

Can this tool fix the problems it finds in a commit?

No, it only inspects and reports; it never modifies code, applies patches, or commits changes. Findings that need fixes are handed off to a separate bug-fix workflow, and the user decides the next action.

Does commit review handle merge commits and large diffs?

Yes, merge commits are diffed against the first parent to focus on the merged content. The summary diff is truncated at 500 lines by default, and the complete diff is always available in the raw.diff output file.

What are the limitations of automated commit review?

It does not run builds or tests, so verification relies on a conclusion self-check covering evidence traceability, grading, and dimension coverage. Line numbers reference the current working tree, which may drift from the commit's historical state.