draft-commit

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

Updated Nov 13, 2025
One-click install
npx skills add https://github.com/AbeJitsu/Game-Settings-Panel --skill draft-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-commit
Source: https://github.com/AbeJitsu/Game-Settings-Panel/tree/main/.claude/skills/draft-commit
Command: npx skills add https://github.com/AbeJitsu/Game-Settings-Panel --skill draft-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, concise, and informative commit messages can be a tedious task. This Skill automates the process, helping you articulate your changes effectively for better collaboration, clearer project history, and easier code reviews.

Core Features & Use Cases

  • Staged Changes Analysis: Automatically reviews your git diff --cached to understand the nature and scope of your work.
  • Intent Inference: Categorizes changes (e.g., feature, bug fix, refactor, documentation) and identifies their impact on the codebase.
  • Configurable Style: Adjusts the message tone (supportive, concise) and format (descriptive, conventional) to match your team's preferences.
  • Use Case: After staging your code changes, use this Skill to instantly generate a professional commit message that explains both what you did and why it matters, saving you time and ensuring consistency.

Quick Start

Draft a commit message for my staged changes.

Frequently Asked Questions about draft-commit

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

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

Staged changes are analyzed through `git diff --cached` to automatically generate a commit message. The Skill infers change type, scope, and intent, then produces a descriptive, ready-to-copy message that explains both what changed and why it matters.

Can I customize the commit message format and style?

Yes. Commit message generation supports configurable requirements including message style (supportive or concise), format (descriptive or conventional), length constraints, and whether to include context and file counts via config.json settings.

What types of changes does the commit message analyzer recognize?

The analyzer categorizes changes into feature additions, bug fixes, refactors, and documentation updates. It identifies the scope and impact of each change type to create contextually appropriate commit messages.

Do I need to write the commit message myself after staging?

No. After staging your code changes with git, the Skill automatically drafts a professional commit message with both the message text and an analysis payload for review before committing.

What's the best way to ensure consistent commit messages across a team?

Automated commit message generation enforces consistency by applying configurable style and format rules uniformly. All team members stage their changes, then generate messages following the same conventions without manual effort.