terse-semantic-commits

Standardize commit messages to follow Conventional Commits format.

8|Updated Feb 4, 2026

Search Tags:#git #commit #formatting #scope #semantic #conventional-commits #imperative

Ready to run

npx skills add https://github.com/hutchic/.cursor --skill terse-semantic-commits

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: terse-semantic-commits
Source: https://github.com/hutchic/.cursor/tree/main/.cursor/skills/git/terse-semantic-commits
Command: npx skills add https://github.com/hutchic/.cursor --skill terse-semantic-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent or unclear commit messages hinder code reviews, debugging, and project automation.

Core Features & Use Cases

Enforces the Conventional Commits format with a structured type, optional scope, and a concise description.
Guides the use of imperative mood and ensures descriptions are short and actionable.
Supports deriving scope from changed files and provides concrete examples for common changes.

Quick Start

Craft a sample commit message for the latest change using the <type>(<scope>): <description> format.

Frequently Asked Questions about terse-semantic-commits

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

FAQPage Schema

How do I format git commit messages using conventional commits?▼

Format git commit messages using the structured <type>(<scope>): <description> syntax. This standardization enforces a concise type, optional scope derived from changed files, and a short description to ensure consistency across project workflows.

What is imperative mood in semantic commit messages?▼

Imperative mood in semantic commit messages requires writing descriptions as direct commands, such as "add" or "fix". This approach ensures the commit message reads as a concise, actionable instruction rather than a past-tense statement.

How do I derive the scope for a conventional commit from changed files?▼

Derive the conventional commit scope from changed files by extracting the relevant module or component name. This ensures the commit message accurately reflects the specific area of the codebase impacted by the changes.

Why use standardized semantic commit messages for pull requests?▼

Standardized semantic commit messages for pull requests improve code reviews, debugging, and project automation. Consistent type and scope formatting allows automated tools to track changes and generate release notes efficiently.

Can I use conventional commits for daily commits and release workflows?▼

Yes, you can use conventional commits for daily commits and release workflows. The standardized type, scope, and description format supports both routine development tracking and automated release processes.