draft-commit-message

Generate conventional commit messages from staged Git changes.

1|Updated Jan 5, 2026

Search Tags:#git #commit #scope #conventional-commits #staged-changes #type #message-draft

Ready to run

npx skills add https://github.com/eburairu/Squat-Tracker --skill draft-commit-message

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: draft-commit-message
Source: https://github.com/eburairu/Squat-Tracker/tree/main/.agent/skills/draft-commit-message
Command: npx skills add https://github.com/eburairu/Squat-Tracker --skill draft-commit-message

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers automatically craft conventional commit messages from the changes staged in Git, reducing manual drafting and ensuring consistency.

Core Features & Use Cases

Staged-change analysis: Inspects git diff --staged to understand what changed.
Conventional-Commits mapping: Suggests a commit type (feat/fix/docs/chore/refactor/etc.) and an optional scope.
Structured message generation: Produces a complete draft with title and body suitable for commit messages.

Quick Start

Use the tool after staging changes with git add, then run the tool to generate a draft commit message.

Frequently Asked Questions about draft-commit-message

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

FAQPage Schema

How do I generate conventional commit messages from staged changes?▼

To generate conventional commit messages, use a tool that inspects git diff --staged to identify the change type and optional scope, then drafts a structured message ready for your commit.

What is a conventional commit and how does scope work?▼

A conventional commit is a structured message format that uses a type like feat or fix and an optional scope to categorize changes, ensuring consistent and meaningful git history across development teams.

Can I use this to draft commit messages for bugfix changes across teams?▼

Yes, this approach analyzes your staged Git changes and suggests an appropriate type, such as fix or feat, along with an optional scope to ensure commit messages remain consistent for team workflows.

How do I analyze git diff to suggest a commit type and scope?▼

By parsing the staged changes in git diff --staged, the mechanism identifies what was modified and maps the modifications to a conventional commit type and optional scope to produce a structured draft.

Do I need to stage changes with git add before drafting a commit message?▼

Yes, you must stage your desired changes using git add first, because the message drafting process specifically analyzes the git diff --staged output to understand what changed.