git-commit

Generate standardized Git commit messages following project conventions and Conventional Commits.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/krissss/skills --skill git-commit-krissss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/krissss/skills/tree/main/skills/git-commit
Command: npx skills add https://github.com/krissss/skills --skill git-commit-krissss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create clear, consistent, and规范 (standardized) Git commit messages, prioritizing your project's existing conventions and supporting the Conventional Commits standard.

Core Features & Use Cases

  • Project Convention Adherence: Analyzes your project's commit history to identify and follow its specific style (type names, language, issue referencing).
  • Conventional Commits Support: Generates messages adhering to the <type>(<scope>): <subject>\n\n<body>\n\n<footer> format when no project convention is found.
  • Intelligent Change Analysis: Helps identify and separate unrelated changes within a commit to maintain atomic commits.
  • Merge Conflict Prevention: Guides you on whether to amend a commit or create a new one based on your branch's status relative to its upstream.
  • Use Case: When you've made several related changes to a feature, use this Skill to generate a commit message that accurately reflects the changes and fits your team's established Git workflow.

Quick Start

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

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write a git commit message that follows my project's existing conventions?

To write a git commit message that follows project conventions, this skill analyzes your commit history to identify specific styles like type names, language, and issue referencing, and automatically generates matching messages.

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

The conventional commits format structures a git commit message using `<type>(<scope>): <subject>\ \ <body>\ \ <footer>`, which this skill automatically applies when no existing project convention is detected.

How do I separate unrelated code changes into atomic git commits?

To separate unrelated code changes into atomic git commits, this skill intelligently analyzes your staged changes and helps identify distinct modifications to ensure each commit represents a single logical update.

Should I amend a git commit or create a new one to prevent merge conflicts?

To prevent merge conflicts when deciding to amend a git commit or create a new one, this skill guides you by evaluating your current branch status relative to its upstream branch.

Can I generate a standardized git commit message for multiple related feature changes?

Yes, you can generate a standardized git commit message for multiple related feature changes by using this skill to accurately reflect the updates while fitting your team's established version control workflow.

Does the git commit message generator work without external dependencies?

Yes, the git commit message generator works without external dependencies, requiring only your project's uncommitted changes and existing commit history to analyze conventions and output standardized messages.