C
conventional-commit
by @githubv
4.5(318)
Provide tips and workflows for generating conventional commit messages using a structured XML format, helping users create standardized descriptive commits.
Installation
npx skills add github/awesome-copilot --skill conventional-commitcompare_arrows
Before / After Comparison
1 组Before
Non-standard commit messages lead to chaotic version history, making it difficult to track feature changes and fixes. Team members struggle to understand the intent of code commits, affecting collaboration efficiency.
After
Automatically generate standardized commit messages, ensuring a clear and readable version history that is easy to trace. This significantly improved team collaboration efficiency and project maintainability.
SKILL.md
Instructions
<description>This file contains a prompt template for generating conventional commit messages. It provides instructions, examples, and formatting guidelines to help users write standardized, descriptive commit messages in accordance with the Conventional Commits specification.</description>
Workflow
Follow these steps:
- Run
git statusto review changed files. - Run
git difforgit diff --cachedto inspect changes. - Stage your changes with
git add <file>. - Construct your commit message using the following XML structure.
- After generating your commit message, Copilot will automatically run the following command in your integrated terminal (no confirmation needed):
git commit -m "type(scope): description"
- Just execute this prompt and Copilot will handle the commit for you in the terminal.
Commit Message Structure
<commit-message>
<type>feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert</type>
<scope>()</scope>
<description>A short, imperative summary of the change</description>
<body>(optional: more detailed explanation)</body>
<footer>(optional: e.g. BREAKING CHANGE: details, or issue references)</footer>
</commit-message>
Examples
<examples>
<example>feat(parser): add ability to parse arrays</example>
<example>fix(ui): correct button alignment</example>
<example>docs: update README with usage instructions</example>
<example>refactor: improve performance of data processing</example>
<example>chore: update dependencies</example>
<example>feat!: send email on registration (BREAKING CHANGE: email service required)</example>
</examples>
Validation
<validation>
<type>Must be one of the allowed types. See <reference>https://www.conventionalcommits.org/en/v1.0.0/#specification</reference></type>
<scope>Optional, but recommended for clarity.</scope>
<description>Required. Use the imperative mood (e.g., "add", not "added").</description>
<body>Optional. Use for additional context.</body>
<footer>Use for breaking changes or issue references.</footer>
</validation>
Final Step
<final-step>
<cmd>git commit -m "type(scope): description"</cmd>
<note>Replace with your constructed message. Include body and footer if needed.</note>
</final-step>
User Reviews (0)
Write a Review
Effect
Usability
Docs
Compatibility
No reviews yet
Statistics
Installs12.0K
Rating4.5 / 5.0
Version
Updated2026年5月23日
Comparisons1
User Rating
4.5(318)
5
23%
4
51%
3
23%
2
2%
1
0%
Rate this Skill
0.0
Compatible Platforms
🔧Claude Code
🔧OpenClaw
🔧OpenCode
🔧Codex
🔧Gemini CLI
🔧GitHub Copilot
🔧Amp
🔧Kimi CLI
Timeline
Created2026年3月16日
Last Updated2026年5月23日