semantic-commit

Generate conventional-commit messages from staged changes with optional scope and body.

4|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonmagic/skills --skill semantic-commit-jonmagic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semantic-commit
Source: https://github.com/jonmagic/skills/tree/main/skills/semantic-commit
Command: npx skills add https://github.com/jonmagic/skills --skill semantic-commit-jonmagic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams produce consistent commit messages that follow the conventional-commit format, reducing ambiguity and improving changelog quality.

Core Features & Use Cases

  • Enforces conventional commit structure: type(scope): subject
  • Supports an optional scope and a concise subject under 72 chars
  • Provides a body to explain the what and why for non-trivial changes

Quick Start

Stage your changes and run the semantic-commit action to generate a conventional-commit message, for example: feat(auth): add OAuth login

Frequently Asked Questions about semantic-commit

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

FAQPage Schema
How do I generate semantic commit messages from staged git changes?

To generate semantic commit messages, you stage your git changes and run the generator to enforce the conventional-commit format. It produces a structured message with an optional scope and a subject under 72 characters.

What is the conventional commit format for git workflows?

The conventional commit format structures git messages as type(scope): subject. It requires a present-tense subject line under 72 characters and allows a body to explain the what and why for non-trivial changes.

How do I enforce consistent commit messages across my version control workflow?

You enforce consistent commit messages by applying the conventional-commit format to your staged changes. This reduces ambiguity and improves changelog quality by standardizing the type, scope, and subject.

When do I need to include a body in a conventional commit?

You include a body in a conventional commit for non-trivial changes. The body is used to explain exactly what the change does and why it was made, complementing the concise 72-character subject line.

Does this conventional commit generator support scoped messages?

Yes, the semantic commit generator supports an optional scope within the conventional-commit format. This allows you to categorize changes by specific modules, such as generating feat(auth): add OAuth login.