skills.rest
7loro
7loroCOMMUNITY
Explore all skills by this author →
GitHub

make-commit-msg

Generates five Git commit-message candidates from staged changes with optional type control.

1|Updated Aug 25, 2024
Search Tags:#automation#git#consistency#commit messages#command-line#staged changes
One-click install
npx skills add https://github.com/7loro/dotfiles --skill make-commit-msg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: make-commit-msg
Source: https://github.com/7loro/dotfiles/tree/main/dot_config/agents/skills/make-commit-msg
Command: npx skills add https://github.com/7loro/dotfiles --skill make-commit-msg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes staged Git changes and generates five commit message candidates to streamline your commit history and maintain consistency across the project.

Core Features & Use Cases

  • Automated message generation: Produces five messages from the current staged diff.
  • Type control: If you provide a type, all candidates adopt that type; otherwise, an appropriate type is chosen (feat, fix, refactor, build, docs, style, test, chore).
  • Output format and constraints: Each message follows the pattern {type}: {description}, one per line, without numbers or additional formatting, and messages are produced in Korean.
  • Use Case: When preparing commits after a set of changes, run this skill to quickly draft consistent messages for review.

Quick Start

Run the skill to generate five commit messages from your current staged changes. If you want to lock a specific type, provide it as an argument, e.g., "make-commit-msg feat".

Frequently Asked Questions about make-commit-msg

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

FAQPage Schema
How do I generate commit messages from staged Git changes?▼

You generate commit messages from staged Git changes by running the tool to analyze the current staging area diff and output five candidate messages. This process streamlines your commit history and maintains project consistency.

Can I force a specific commit type like feat or fix when generating messages?▼

Yes, you can force a specific commit type by providing it as an argument, such as "make-commit-msg feat". If no type is provided, the tool automatically selects an appropriate type from feat, fix, refactor, build, docs, style, test, or chore.

What format do the generated Git commit message candidates follow?▼

The generated commit message candidates follow the exact format of {type}: {description}, printed one per line without numbers. The descriptions are written in Korean and use the imperative mood to directly state the staged changes.

Does this tool work with unstaged files in my Git repository?▼

No, this tool exclusively analyzes the current Git staging area. You must stage your desired file changes using Git commands before running the tool to generate the five commit message candidates.

What is the best way to maintain commit consistency across a project?▼

Using an automated commit message generator is the best way to maintain consistency. It analyzes your staged changes and outputs standardized messages with predefined types, ensuring every commit follows the same structural pattern.

Related Skills

Explore More Software Engineering Skills→
ss49919201ss49919201

git-add-commit

Stage git changes and generate commit messages from diffs.

Community
Basic
ctrsploitctrsploit
153

commit-message

Generate semantic Git commit messages from staged changes using Conventional Commits.

Official
Intermediate
AmidVoshakulAmidVoshakul

git-hooks-automation

Automate Git hook configuration for linting, formatting, and commit message validation.

Community
Advanced
kevinrobaynakevinrobayna

commit

Generate conventional Git commit messages from analyzed code changes.

Community
Intermediate