skills.rest
BangDori
BangDoriCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Generate Conventional Commits messages from staged and unstaged changes.

11|Updated Jan 25, 2026
Search Tags:#git#code review#version control#commit#conventional commits
One-click install
npx skills add https://github.com/BangDori/prowl --skill commit-bangdori
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/BangDori/prowl/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/BangDori/prowl --skill commit-bangdori

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of creating Git commit messages that adhere to the Conventional Commits specification, ensuring consistency and clarity in your project's commit history.

Core Features & Use Cases

  • Automated Commit Message Generation: Analyzes staged and unstaged changes to suggest appropriate commit types and messages.
  • Conventional Commits Adherence: Enforces a standardized format for commit messages, including type, scope, subject, and body.
  • Use Case: After making several code changes, use this Skill to generate a feat commit for a new feature, a fix commit for a bug, and a refactor commit for code improvements, all formatted correctly.

Quick Start

Use the commit skill to generate a conventional commit message for 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 generate conventional commits for staged git changes?▼

To generate conventional commits, this Skill analyzes your staged and unstaged git changes and suggests a formatted commit message with the correct type, scope, subject, and body.

What is the conventional commits format for a git commit message?▼

The conventional commits format structures git messages by categorizing changes into specific types like feat, fix, refactor, style, docs, test, chore, perf, and ci, ensuring a clear project history.

How do I categorize code changes into feat, fix, or refactor commit types?▼

You can categorize code changes by using this Skill to analyze your staged differences; it automatically determines whether your modifications represent a new feature, a bug fix, or a code refactor.

Can I use this to write git commit messages for both staged and unstaged files?▼

Yes, the Skill analyzes both staged and unstaged file changes to provide guidance on subject and body content, ensuring clear and consistent conventional commit messages across your repository.

What's the best way to enforce consistent git commit messages in version control?▼

The best way to enforce consistent git commit messages in version control is to automate generation using the Conventional Commits specification, standardizing types like feat and fix for all updates.

Does the commit Skill require any specific git hooks or dependencies to work?▼

No specific git hooks or external dependencies are required; the Skill directly analyzes your staged and unstaged changes to generate standardized conventional commit messages.

Related Skills

Explore More Software Engineering Skills→
run6270run6270
1

Git Commit Helper

Generate git commit messages following the Conventional Commits specification.

Community
Basic
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
mathiasbourgoinmathiasbourgoin
2

git-conventions

Standardize git commit messages, branch names, and pull request descriptions.

Community
Intermediate
JannaelJannael
16

caveman-commit

Generates Git commit messages adhering to Conventional Commits format with strict subject and body rules.

Community
Intermediate