skills.rest
laceto
lacetoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit

Create Conventional Commits with type, scope, and description from git diffs.

1|Updated Jun 25, 2025
Search Tags:#git#developer tools#version control#commit#conventional commits#code history
One-click install
npx skills add https://github.com/laceto/rss_feed --skill git-commit-laceto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/laceto/rss_feed/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/laceto/rss_feed --skill git-commit-laceto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users create standardized, semantic git commits following the Conventional Commits specification, ensuring a clean and understandable project history.

Core Features & Use Cases

  • Conventional Commits: Generates commits with type(scope): description format.
  • Type Support: Supports feat, fix, docs, refactor, test, perf, build, ci, chore, revert.
  • Use Case: When you've finished a new feature, use this skill to commit your changes with a feat type and a clear description.

Quick Start

Use the git-commit skill to create a commit for your staged changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I create conventional commits automatically from my git diff?▼

Automating conventional commits involves analyzing your git diff to determine the appropriate type, scope, and description. This Skill parses staged changes to generate a semantic commit message adhering to the specification.

What is the conventional commits format for structuring git history?▼

The conventional commits format structures git history using a `type(scope): description` syntax. It categorizes atomic changes using types like feat, fix, docs, refactor, test, perf, build, ci, chore, and revert.

Can I use this to generate a fix commit for a bug in a specific scope?▼

Yes, you can generate a fix commit for a specific scope. The Skill analyzes your staged changes and applies the `fix` type with the appropriate scope and description to ensure a clean project history.

Does this support all standard commit types for version control?▼

It supports standard version control commit types including feat, fix, docs, refactor, test, perf, build, ci, chore, and revert. This ensures your semantic git commits cover a wide range of development activities.

When do I need to use semantic commits instead of regular git commits?▼

You need semantic commits when you want a standardized and understandable project history. By using the Conventional Commits specification, you ensure changes are atomic and easily trackable for future analysis.

Related Skills

Explore More Software Engineering Skills→
cipherstashcipherstash
17

Commit Workflow

Run pre-commit checks and create atomic conventional commits.

Official
Intermediate
CuriousLearnerCuriousLearner
27

changelog-generator

Generates project changelogs from Git commits using standard formatting.

Community
Intermediate
dstanberrydstanberry
7

conventional-commit

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

Community
Intermediate
camilooscargbaptistacamilooscargbaptista
7

pr-description

Generate What/Why/How summaries for GitHub or GitLab PRs with risk assessments.

Community
Advanced