commit

Generate conventional commits with automatic type and scope detection.

59|3|Updated Jan 23, 2020

Search Tags:#automation #git #commit #release-notes #conventional-commits #type-detection #scopes

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool automates the creation of conventional commits with automatic type and scope detection, solving the challenge of inconsistent or hard-to-read commit messages.

Core Features & Use Cases

Automatic type and scope detection from code changes.
Enforces conventional commits format and single-commit-per-change discipline.
Useful for teams implementing conventional commits, changelog generation, and automated release notes.

Quick Start

Invoke /commit to generate a conventional commit from your staged 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 with type and scope detection?▼

To automate conventional commits, you map staged code changes to a specific type, infer the scope, and format a deterministic commit message, ensuring a cohesive history for automated release notes.

What is the best way to generate consistent git commit messages for release notes?▼

Generating consistent git commit messages for release notes is best achieved by enforcing conventional commit formats and single-commit-per-change discipline, which maps changes to types and infers scopes automatically.

How do I create an atomic conventional commit from staged changes?▼

To create an atomic conventional commit from staged changes, you invoke a commit automation tool that detects the type and scope from the diff and formats the final commit message deterministically.

Does automated type detection work for enforcing single-commit-per-change discipline?▼

Automated type detection works for single-commit-per-change discipline by mapping each cohesive set of staged changes to a specific conventional commit type and inferring its scope before formatting the message.

When do I need conventional commits with automatic scope inference in my workflow?▼

You need conventional commits with automatic scope inference when your software development workflow requires cohesive commit histories, deterministic messaging, and automated changelog or release notes generation.