skills.rest
spraby
sprabyCOMMUNITY
Explore all skills by this author →
GitHub

ai-factory.commit

Generate git commit messages from staged changes with automatic detection of commit type and a concise, human-readable summary of the intended semantic changes.

Updated Mar 31, 2025
Search Tags:#git#developer tools#code review#version control#commit#conventional commits
One-click install
npx skills add https://github.com/spraby/api --skill ai-factory-commit-spraby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-factory.commit
Source: https://github.com/spraby/api/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/spraby/api --skill ai-factory-commit-spraby

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of well-formatted commit messages, ensuring consistency and adherence to the Conventional Commits specification, which improves project history readability and automated changelog generation.

Core Features & Use Cases

  • Conventional Commits: Generates commit messages following the <type>(<scope>): <subject> format.
  • Type Determination: Automatically suggests commit types like feat, fix, docs, style, refactor, perf, test, build, ci, chore.
  • Scope Identification: Infers scope from file paths or user-provided arguments.
  • Use Case: After making changes to the user authentication module, you can invoke this skill to generate a feat(auth): add new login endpoint commit message.

Quick Start

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

Frequently Asked Questions about ai-factory.commit

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

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

You can generate conventional commit messages by invoking this Skill against your staged Git changes, which automatically determines the type, scope, and subject line for your commit.

What is the Conventional Commits format for writing Git commit messages?▼

The Conventional Commits format structures Git commit messages as `<type>(<scope>): <subject>`, utilizing types like feat, fix, docs, and refactor to improve project history readability and automate changelog generation.

How do I automatically determine the scope for a conventional commit?▼

The scope for a conventional commit is automatically inferred by analyzing the file paths of your staged changes, or you can explicitly provide an optional scope argument to override the inferred value.

Can I review the generated commit message before it is applied to my Git history?▼

Yes, the Skill provides a review step before committing, allowing you to verify the generated type, scope, and subject line against your staged changes before finalizing the Git commit.

What commit types are supported when generating semantic Git commit messages?▼

Supported semantic Git commit types include feat, fix, docs, style, refactor, perf, test, build, ci, and chore, covering standard software engineering version control scenarios.

Related Skills

Explore More Software Engineering Skills→
thecarlothecarlo
1

commit-message

Generate semantic git commit messages from staged changes.

Community
Advanced
devantler-techdevantler-tech
2

conventional-release

Write Conventional Commit PR titles and commit messages for automated releases.

Official
Intermediate
greyhaven-aigreyhaven-ai
29

grey-haven-linear-workflow

Automate Linear issue creation, branch naming, and PR integration with Git workflows.

Community
Basic
xabierlameiroxabierlameiro

git-commit

Generate Conventional Commits messages by analyzing code diffs and staging files.

Community
Intermediate