skills.rest
ThinkInAIXYZ
ThinkInAIXYZOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-commit

Generate Conventional Commits messages with type, scope, subject, body, and footers.

6.2k|712|Updated Feb 14, 2025
Search Tags:#git#workflow#versioning#commit#conventional-commits#message-generation
One-click install
npx skills add https://github.com/ThinkInAIXYZ/deepchat --skill git-commit-thinkinaixyz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/ThinkInAIXYZ/deepchat/tree/main/resources/skills/git-commit
Command: npx skills add https://github.com/ThinkInAIXYZ/deepchat --skill git-commit-thinkinaixyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams generate well-structured Git commit messages that conform to the Conventional Commits specification, reducing ambiguity and the need for manual edits.

Core Features & Use Cases

  • Enforce standard formats: Generate messages that follow <type>(<scope>): <subject> with an optional body and footer as needed.
  • Guided type/scope selection: Suggest appropriate types (feat, fix, docs, style, refactor, perf, test, build, ci, chore) and optional scope based on the changes.
  • Use Case: Before merging a feature branch, run this skill to produce a complete commit message that clearly describes the change and references related issues if needed.

Quick Start

Generate a conventional commit message for the latest changes in the working tree.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commit messages for my Git workflow?▼

This Skill generates conventional commit messages by enforcing the <type>(<scope>): <subject> format with an optional body and footer, reducing ambiguity and manual edits in your Git workflow.

What types and scopes does the conventional commits specification include?▼

The conventional commits specification includes types like feat, fix, docs, style, refactor, perf, test, build, ci, and chore. This Skill suggests appropriate types and optional scopes based on your specific working tree changes.

Can I add a body and footer to my conventional commit message?▼

Yes, you can add an optional body and footer to your conventional commit message. This Skill formats the complete message according to the Conventional Commits specification, allowing you to reference related issues in the footer as needed.

When should I use a conventional commit message generator before merging?▼

You should use a conventional commit message generator before merging a feature branch. This Skill produces a complete commit message that clearly describes the change and references related issues, ensuring your Git history remains structured and unambiguous.

Do I need any dependencies to enforce conventional commit formats?▼

No dependencies are required to enforce conventional commit formats with this Skill. It operates independently to generate well-structured Git commit messages that conform strictly to the Conventional Commits specification without external tools.

Related Skills

Explore More Software Engineering Skills→
GLaDO8GLaDO8

smartcommit

Generates concise Git commit messages and commits staged or unstaged changes.

Community
Basic
ccfccf

changelog-automation

Generate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.

Community
Advanced
ivyivy
9

commit

Stage intended files and write conventional, why-focused commit messages.

Community
Advanced
sgcarstrendssgcarstrends
21

changelog

Generate CHANGELOG.md from conventional commits using semantic-release.

Official
Advanced