commit

Generate conventional Git commit messages from analyzed code changes.

Updated Feb 29, 2020
One-click install
npx skills add https://github.com/kevinrobayna/dotfiles --skill commit-kevinrobayna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kevinrobayna/dotfiles/tree/main/claude/dot-claude/skills/commit
Command: npx skills add https://github.com/kevinrobayna/dotfiles --skill commit-kevinrobayna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of well-structured Git commit messages, ensuring consistency and adherence to conventional commit standards, saving developers time and improving code history clarity.

Core Features & Use Cases

  • Conventional Commits: Automatically generates commit messages following the type(scope): description format.
  • Change Analysis: Analyzes staged and unstaged changes to inform the commit message.
  • Contextual Body: Creates a descriptive body explaining the 'why' behind the changes.
  • Use Case: After making several changes to a feature, invoke this skill to generate a commit message like feat(auth): implement two-factor authentication with a detailed explanation of the implementation choices.

Quick Start

Use the commit skill to create a git commit message for your current changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for staged and unstaged Git changes?

To generate conventional commit messages, this Skill analyzes your staged and unstaged Git changes and automatically formats them into the standard type(scope): description structure, providing a structured code history.

What is the conventional commits format and how does it improve my code history?

The conventional commits format structures Git messages as type(scope): description. This Skill applies this standard to your code changes, improving code history clarity and saving development time by ensuring consistent, structured commit messages.

Can I automatically generate a contextual body explaining the why behind my Git commits?

Yes, you can generate a contextual body for Git commits. This Skill analyzes your code changes to create a descriptive body explaining the implementation choices and the reasoning behind your modifications.

Do I need Git command-line tools installed to analyze code changes for commit messages?

Yes, you need Git command-line tools installed. This Skill requires the Git command-line environment to analyze your code changes and generate properly formatted conventional commit messages for your development workflow.

Why does my automated Git commit message include a type and scope?

Automated Git commit messages include a type and scope to adhere to conventional commit standards. This Skill parses your code changes to determine the appropriate type, such as feat, and scope to ensure a structured and readable commit history.

When should I not use automated conventional commit generation for version control?

You should avoid automated conventional commit generation when your version control changes require highly specific, custom messaging or when Git command-line tools are unavailable, as this Skill relies on analyzing code changes to format standard messages.