write-commit-message

Generate standardized commit messages with change type identification.

92|7|Updated Dec 11, 2025

Search Tags:#code review #standardization #issue tracking #commit message #source control

Ready to run

npx skills add https://github.com/encero-systems/incan --skill write-commit-message-encero-systems

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-commit-message
Source: https://github.com/encero-systems/incan/tree/main/.agents/skills/write-commit-message
Command: npx skills add https://github.com/encero-systems/incan --skill write-commit-message-encero-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of writing standardized commit messages efficiently, adhering to a consistent commit naming convention for ease of review and maintainability.

Core Features & Use Cases

Standardized Naming Convention: Follows a strict format that helps maintain readability and consistency in commit logs.
Change Type Identification: Automatically identifies change types from the code changes.
Issue Reference Extraction: Automatically extracts issue IDs from branch names and task context for better traceability.
Commit Message Drafting: Provides a clear guide on drafting both titles and bodies of commit messages.
Output Formatting: Generates output tailored to the user's request, including only the title or the full commit text.

Quick Start

Generate a commit message draft with the command: write-commit-message.

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 standardized commit message automatically?▼

To generate a standardized commit message, you can use a command that automates drafting by identifying change types from your code changes and extracting issue references from branch names to ensure source control maintainability.

What is the best way to format commit messages for code review?▼

The best way to format commit messages for code review is to follow a standardized naming convention that automatically identifies change types and extracts issue IDs, ensuring readability and consistency across commit logs.

How do I extract issue tracking IDs from branch names for a commit message?▼

Extracting issue tracking IDs from branch names for a commit message is handled automatically by analyzing the branch name and task context, linking the commit directly to the relevant issue for better traceability.

Can I generate only the commit message title without the full body text?▼

Yes, you can generate only the commit message title without the full body text by tailoring the output formatting to your specific request, providing either just the title or the complete commit message draft.

Do I need to provide user input to identify change types in my commit message?▼

Yes, you need to provide user input to identify change types, as the commit message generation process requires your context to infer the specific nature of the code changes and apply the correct standardized format.