commit

Generate conventional git commits from staged diffs with inferred type and scope.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/dohernandez/claude-skills --skill commit-dohernandez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/dohernandez/claude-skills/tree/main/plugins/commit/skills/commit
Command: npx skills add https://github.com/dohernandez/claude-skills --skill commit-dohernandez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create standardized git commits following the Conventional Commits specification by analyzing diffs and guiding the message generation to ensure consistency and clarity across the project history.

Core Features & Use Cases

  • Infer commit type and scope from code changes and staged diffs.
  • Enforce conventional commit formatting and safety checks to prevent problematic commits.
  • Support project-specific scopes via /commit configure and adapt to different installation models.
  • Provide guided pre-commit checks and deterministic messaging to improve code review quality.

Quick Start

Invoke /commit in a project to generate a conventional commit for staged changes after review.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commits automatically from staged git diffs?

To generate conventional commits from staged git diffs, invoke the /commit command in your project. The tool analyzes the staged changes to infer the commit type and scope, enforcing the conventional commit format automatically.

What is the conventional commit format and how does scope inference work?

The conventional commit format standardizes git history by categorizing changes into types and scopes. This tool analyzes your code diffs to automatically infer the correct type and scope based on the modified files and context.

Can I configure project-specific scopes for conventional commits?

Yes, you can configure project-specific scopes using the /commit configure command. This allows the automated commit generation to adapt to your project's specific installation model and defined scope boundaries.

Does automated commit generation apply safety checks before creating a commit?

Yes, automated commit generation applies safety checks before finalizing the message. These pre-commit checks enforce conventional formatting and prevent problematic commits to ensure consistency and improve code review quality.

What is the best way to standardize git workflow history across different software projects?

The best way to standardize git history is using automated conventional commit generation that applies across software projects regardless of language. It enforces deterministic messaging and formatting rules consistently.