conventional-commit

Name: conventional-commit
Availability: InStock
Author: aSafeLobotomy

Generate Conventional Commit messages from staged Git diffs.

7|2|Updated Dec 14, 2025

Search Tags:#git #changelog #commit-message #conventional-commits #scopes #release-versioning

Ready to run

npx skills add https://github.com/asafelobotomy/iCloud-Drive-Downloader --skill conventional-commit-asafelobotomy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/asafelobotomy/iCloud-Drive-Downloader/tree/main/.github/skills/conventional-commit
Command: npx skills add https://github.com/asafelobotomy/iCloud-Drive-Downloader --skill conventional-commit-asafelobotomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commit messages make your project history easier to read, automate, and release consistently without debates about formatting.

Core Features & Use Cases

Conventional Commit structure: Produces messages that follow the Conventional Commits spec, including an appropriate type, optional scope, and an imperative subject.
Detailed guidance from staged changes: Helps you inspect the staged diff to select the correct type and scope that reflect what you actually changed.
Breaking change support: Adds the proper ! marker and BREAKING CHANGE: footer when relevant, so tooling can detect semver implications.

Quick Start

Ask the AI to generate a Conventional Commit for your staged changes by first running git diff --cached and then producing the final message for you to approve.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema

How do I write conventional commit messages for staged Git changes?▼

Conventional commit messages are generated by extracting staged Git diffs, selecting a valid type and optional scope, formatting a ≤72 character imperative subject, and optionally appending a wrapped body or breaking-change footer.

What is the conventional commits format for breaking changes?▼

The conventional commits format for breaking changes uses an exclamation mark after the type or scope, along with a BREAKING CHANGE: footer, allowing automation tooling to detect semantic versioning implications accurately.

How do I add scopes to my commit messages for better changelog automation?▼

Scopes are added to commit messages by inspecting the staged diff to identify the affected module, appending the scope in parentheses after the commit type, which helps categorize changes for automated changelog generation.

Does this support different commit types like fix, refactor, and CI?▼

Yes, this supports feature, fix, documentation, refactor, performance, test, build, CI, and chore workflows, allowing you to standardize commit history across typical Git-based development tasks.

What's the best way to automate release versioning from Git commit history?▼

Automating release versioning from Git commit history requires standardizing commit messages with structured types, optional scopes, and breaking-change markers so tooling can parse semantic versioning implications consistently.