conventional-commit

Inspect staged and unstaged changes to generate and execute conventional commits.

7|Updated Nov 30, 2019

Search Tags:#automation #git #commit-message #conventional-commit #type #scopes

Ready to run

npx skills add https://github.com/dstanberry/dotfiles --skill conventional-commit-dstanberry

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/dstanberry/dotfiles/tree/main/ai/claude/skills/conventional-commit
Command: npx skills add https://github.com/dstanberry/dotfiles --skill conventional-commit-dstanberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation and execution of conventional commits by analyzing repository changes, producing a standards-compliant commit message, and performing the git commit without requiring user input.

Core Features & Use Cases

Inspects staged and unstaged changes to determine the appropriate type (feat, fix, docs, etc.) and scope.
Generates a Conventional Commits-compliant message and applies it via git commit.
Works within typical developer workflows, including staged changes, partial staging, and optional bodies for larger changes.

Quick Start

Inspect the repository for changes, derive a conventional commit message, and run git commit with that message.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema

How do I automate conventional commit messages from staged and unstaged git changes?▼

You can automate conventional commits by inspecting staged and unstaged repository changes to derive a standards-compliant message and execute the git commit without manual input. This Skill analyzes repository state to determine type, scope, and description.

What is the conventional commit format and how does automation determine the type and scope?▼

Conventional commit format structures messages with type, scope, description, and optional body. Automation determines type and scope by inspecting staged and unstaged repository changes, applying the Conventional Commits standard to generate compliant messages.

Does this automated commit message tool work with partial staging in git?▼

Yes, this automated commit tool works within typical developer workflows, including staged changes, partial staging, and optional bodies for larger changes. It inspects repository state to derive compliant messages and performs the git commit.

What's the best way to generate a conventional commit without manual input?▼

The best way to generate a conventional commit without manual input is using an automation Skill that inspects repository changes, derives type, scope, description, and optional body, and applies it via git commit automatically.

Do I need git installed to automate conventional commits for my repository?▼

Yes, you need access to the repository and git to automate conventional commits. The Skill requires git to inspect staged and unstaged changes, derive the standards-compliant commit message, and perform the commit execution.

When should I not use automated conventional commit generation for my changes?▼

Automated conventional commit generation is not ideal when you need custom commit message logic outside the conventional format or when repository changes are too complex for automatic type, scope, and description derivation without manual review.