commit

Generate and validate Conventional Commits-style subject lines for code changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically craft Conventional Commits-style subject lines for the current changes, ensuring consistency and adherence to project conventions.

Core Features & Use Cases

  • Generate a concise subject using the standard type, optional scope, and a short summary.
  • Validate length and allowed types, and provide helpful guidance when adjustments are needed.
  • Ideal for daily commits during feature work, bug fixes, or housekeeping tasks across any git-managed project.

Quick Start

Provide a concise Conventional Commits-style subject for the current changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commits for my git workflow?

You can automate conventional commits by validating changes against the '<type>(<scope>): <summary>' format, enforcing length limits, and generating subject lines for feature development or bug fixes.

What is the correct format for a conventional commit subject line?

A conventional commit subject requires a type, an optional scope, and a summary. The format is '<type>(<scope>): <summary>', and the tool validates length limits and allowed types to ensure compliance.

Can I use this for bug fixes and refactoring across local branches?

Yes, you can use this automation for bug fixes and refactors across local branches. It generates concise conventional commit subjects and supports an optional body for detailed context.

Does the tool validate allowed types and length limits for commit subjects?

The tool validates allowed types and enforces length limits for commit subjects. It provides helpful guidance when adjustments are needed to maintain conventional commit standards.

What's the best way to ensure my commit messages follow project conventions?

To ensure commit messages follow project conventions, use an automation tool that validates the '<type>(<scope>): <summary>' format, enforces type rules, and checks length limits for every code change.