skills.rest
dannys-code-corner
dannys-code-cornerOFFICIAL
Explore all skills by this author →
GitHub

write-commit-message

Drafts commit titles and optional bodies from diffs using workspace naming conventions.

92|7|Updated Dec 11, 2025
Search Tags:#automation#git#commit#diff#commit-message#branch-name#issue-id
One-click install
npx skills add https://github.com/dannys-code-corner/incan --skill write-commit-message-dannys-code-corner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-commit-message
Source: https://github.com/dannys-code-corner/incan/tree/main/.agents/skills/write-commit-message
Command: npx skills add https://github.com/dannys-code-corner/incan --skill write-commit-message-dannys-code-corner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft commit titles and optional bodies that follow a consistent workspace naming convention, saving time and improving clarity across a repository.

Core Features & Use Cases

  • Automated title generation: Derives a concise, descriptive commit title from the actual changes.
  • Optional body: Generates a brief explanation for why the change was made when requested.
  • Format compliance: Ensures the output uses the standard <type> - <short description> (#<issue_id(s)>) pattern and supports chore, bugfix, feature.

Quick Start

Supply the change details or diff and request a commit message drafted in the standard format.

Frequently Asked Questions about write-commit-message

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

FAQPage Schema
How do I generate a git commit message from a diff automatically?▼

Generate a commit message by supplying the diff details for analysis. The tool infers the change type and issue IDs from the changes or branch name, formatting the final title as <type> - <short description> (#<issue_id(s)>).

What format should I use for git commit messages?▼

A standard commit message format follows the pattern <type> - <short description> (#<issue_id(s)>). Supporting chore, bugfix, and feature types, it ensures consistent repository history by inferring the type and issue IDs from branch names and changes.

Can I automatically include issue IDs in my commit message from the branch name?▼

Yes, issue IDs are automatically pulled from the available branch name and changes. The tool appends them to the formatted commit title within the standard <type> - <short description> (#<issue_id(s)>) convention parentheses.

How do I write a commit message body that explains why a change was made?▼

To write a commit message body, request the optional body alongside the title generation. The tool generates a brief explanation for why the change was made, drafted directly from the supplied diff details in the standard format.

Does this commit message generator support different change types like bugfix and chore?▼

Yes, the commit message generator supports bugfix, chore, and feature change types. It automatically infers the appropriate change type from the provided diffs and the branch name to format the final title.

Related Skills

Explore More Software Engineering Skills→
garyjgaryj

commit

Generate conventional Git commit messages with issue references from branch names.

Community
Intermediate
0r0loo0r0loo

Git Skill

Enforce standardized Git commit formats, branch naming, and PR templates.

Community
Intermediate
e-stpierree-stpierre
1

af-git-branch

Create and checkout git branches with standardized kebab-case naming.

Community
Intermediate
whitecloud-savewhitecloud-save
9

commit

Generate Conventional Commits messages in Chinese from staged changes.

Official
Advanced