skills.rest
Takfes
TakfesCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Analyze staged Git diffs and generate Conventional Commits messages.

Updated May 6, 2026
Search Tags:#git#diff analysis#version control#commit#conventional commits#staged changes
One-click install
npx skills add https://github.com/Takfes/indie-scaffolder --skill git-commit-takfes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Takfes/indie-scaffolder/tree/main/components/agent-skills-commands/.agents/skills/git-commit
Command: npx skills add https://github.com/Takfes/indie-scaffolder --skill git-commit-takfes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the guesswork from writing commit messages by turning staged Git changes into clear, conventional, and reviewable commits.

Core Features & Use Cases

  • Diff Analysis: Reviews staged file changes to understand what changed and why it matters.
  • Conventional Formatting: Chooses an appropriate commit type, optional scope, and a concise subject line.
  • Body and Footer Guidance: Helps produce a useful explanation, issue references, and breaking-change notes when needed.
  • Use Case: A developer has finished a focused change and wants a professional commit message that matches team conventions without manually drafting it from scratch.

Quick Start

Use the git-commit skill to analyze my staged changes and generate a conventional commit message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate a conventional commit message from staged git changes?▼

To generate a conventional commit message, you analyze staged git diffs to determine the change type, scope, and subject. This process formats file modifications into a standardized commit structure with a clear body and footer.

What is the best way to format git diffs into feature and fix commits?▼

The best way to format git diffs is by applying Conventional Commits formatting to your staged changes. This approach categorizes modifications into standard types like features, fixes, or refactors, ensuring a reviewable commit history.

Can I use conventional commits for documentation and test updates?▼

Yes, you can use conventional commits for documentation and test updates. The diff analysis categorizes staged changes into appropriate types, including docs and tests, ensuring standardized messages for maintenance tasks.

How do I add breaking change notes and issue references to a commit message?▼

To add breaking change notes and issue references, you include specific footer guidance in the conventional commit structure. This provides a useful explanation and tracks related issues directly within the staged change output.

Does this commit message generator work without manually drafting the subject line?▼

Yes, it works without manual drafting by reviewing staged file changes to understand what changed and why it matters. It then automatically selects a commit type and concise subject line for the output.

Related Skills

Explore More Software Engineering Skills→
OniroHuaverOniroHuaver
30

resolve-merge-conflicts

Resolve Git merge conflicts with compact diffs and conflict summaries.

Community
Intermediate
aberrantCodeaberrantCode
1

release-to-main

Merge dev into main, calculate semantic versions, and publish GitHub releases.

Community
Advanced
miounet11miounet11

Git Smart Commit

Generate conventional commit messages from staged Git changes.

Community
Intermediate
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic