commit

Validate staged Git diffs and generate commit messages for human approval.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/sizukutamago/claude-code-harness --skill commit-sizukutamago
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/sizukutamago/claude-code-harness/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/sizukutamago/claude-code-harness --skill commit-sizukutamago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure commits record meaningful, reviewed changes by validating staged diffs, generating clear commit messages that explain why changes were made, and requiring human approval before committing or pushing, preventing accidental leakage of secrets or undesired history changes.

Core Features & Use Cases

  • Staging verification and safety checks: Inspect staged changes to detect unintended files (secrets, build artifacts) and confirm changes represent a single logical unit.
  • Commit message generation aligned to project history: Produce messages informed by staged diffs and recent commit style, emphasizing why as well as what changed.
  • Human approval workflow and push guidance: Present proposed commit content for human confirmation, enforce hooks and no implicit force-pushes, and advise on PR creation when branch workflows are used.
  • Use case: After cleanup is complete, prepare and present a commit that includes test additions and refactors, verify tests and .gitignore compliance, then commit only after explicit human consent.

Quick Start

Use the commit skill to review staged changes, generate a clear commit message, present it for human approval, and then perform the git commit.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a Git commit message from staged changes?

To generate a Git commit message from staged changes, the skill validates staged diffs and produces messages informed by recent project history, emphasizing why changes were made before requiring human approval.

What is a safe commit workflow for preventing secret leakage?

A safe commit workflow inspects staged changes to detect unintended files like secrets or build artifacts, verifies logical units, and enforces human approval alongside hook safety constraints to prevent accidental leakage.

How do I ensure my staged Git diff represents a single logical unit?

To ensure a staged Git diff represents a single logical unit, the skill performs staging verification that inspects changes to detect unintended files and confirms they represent a cohesive unit before committing.

Can I enforce human approval before pushing Git commits to a remote branch?

Yes, you can enforce human approval before pushing Git commits, as the skill presents proposed commit content for explicit human confirmation, enforces no implicit force-pushes, and advises on PR creation for branch workflows.

How to create review-ready Git commits aligned with project history?

To create review-ready Git commits aligned with project history, the skill analyzes staged diffs and recent commit style to generate clear messages, then validates against hooks and requirements before requesting explicit consent.