commit-review

Enforce conventional commit formats and detect staged secrets in local workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mojwang/macbook-dev-setup --skill commit-review-mojwang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-review
Source: https://github.com/mojwang/macbook-dev-setup/tree/main/.claude/skills/commit-review
Command: npx skills add https://github.com/mojwang/macbook-dev-setup --skill commit-review-mojwang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, bc, bash, and includes scripts (resource) components.

What problem does it solve?

Ensures your team uses consistent commit messages, guards against secrets in staged changes, and prevents risky pushes by automating checks in your local workflow and PR reviews.

Core Features & Use Cases

  • Enforces conventional commit format with allowed types (feat, fix, docs, chore, refactor, test, style, perf, ci, build)
  • Checks for large diffs and suggests splitting into smaller commits
  • Verifies branch safety rules to avoid committing to protected branches and detects staged secrets

Quick Start

Run the commit-review checks before committing to ensure proper messages and secure changes.

Frequently Asked Questions about commit-review

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

FAQPage Schema
How do I enforce conventional commit format checks in a local git workflow?

To enforce conventional commit format checks, you validate commit messages against allowed types like feat, fix, and docs. This Skill applies these rules to local development workflows and pre-commit checks to maintain consistent messages.

How do I detect staged secrets before pushing code changes?

Detecting staged secrets involves scanning your staged changes for sensitive data before finalizing a commit. This Skill performs secret detection during pre-commit checks to guard against accidentally exposing credentials.

Can I prevent commits to protected branches using bash and git scripts?

Yes, you can prevent commits to protected branches using bash and git scripts. This Skill verifies branch safety rules to stop risky pushes directly to protected branches during local development.

What's the best way to check for large diffs and split git commits?

Checking for large diffs requires validating the size of staged changes and suggesting smaller commits. This Skill performs diff-size validations to alert you when changes should be split.

Does this pre-commit code review tool work with feature branches?

Yes, this pre-commit code review tool works with feature branches. It applies conventional commit format checks, diff-size validations, and secret detection across feature branches and protected branches.

Do I need bc installed to run commit message lint scripts?

Yes, you need bc installed along with git and bash to run these commit message lint scripts. These dependencies are required to execute the provided validation scripts for secure code changes.