commit

Generates standardized Conventional Commits messages and commits staged changes from git diff --staged.

Updated Nov 30, 2023
One-click install
npx skills add https://github.com/deanmoses/tacocat-gallery-hosting-aws --skill commit-deanmoses
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/deanmoses/tacocat-gallery-hosting-aws/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/deanmoses/tacocat-gallery-hosting-aws --skill commit-deanmoses

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates clear, conventional commit messages for staged changes and performs the corresponding Git commits, reducing ambiguity and ensuring a clean, standardized project history.

Core Features & Use Cases

  • Conventional Commits formatting: supports types like feat, fix, docs, style, refactor, test, and chore with optional scopes.
  • Automated commit creation: analyzes git diff --staged to craft a concise description and executes the commit.
  • Use Case: when preparing a feature or bug fix for review, use this Skill to generate a standardized commit message and commit the changes automatically.

Quick Start

Stage your changes with git add, then instruct this skill to generate a Conventional Commits message and commit the 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 automatically from staged changes?

To generate conventional commit messages, stage your files with git add and run the skill. It analyzes the staged diff to produce a standardized message with appropriate types like feat or fix, then executes the commit.

What is the conventional commits format and how does it structure git commit messages?

The conventional commits format structures git commit messages by enforcing a type, an optional scope, and a concise description. This standardization reduces ambiguity and ensures a clean project history for features, bug fixes, and documentation.

Can I use this to commit bug fixes and documentation updates with specific types?

Yes, you can commit bug fixes and documentation updates using specific conventional commit types. The skill automatically applies the correct type tag, such as fix or docs, along with an optional scope and a concise description.

Do I need to manually write the commit description after staging my code?

No, you do not need to manually write the commit description. After you stage your code changes, the skill analyzes the git diff to craft a concise, standardized conventional commit message and performs the commit automatically.

Does this skill execute the git commit or just output the generated message?

The skill executes the git commit directly. After analyzing your staged changes to generate the standardized conventional commit message, it performs the corresponding git commit action automatically.

What's the best way to automate version control commits for feature development?

To automate version control commits for feature development, stage your changes and let the skill generate a conventional commit message. It creates standardized commits with types like feat and optional scopes to maintain a clean project history.