github/conventional-commit

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 status to review changed files.
Run git diff or git diff --cached to 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>

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

78/100

Grade

B

Good

Safety

88

Quality

75

Clarity

82

Completeness

68

Summary

This skill guides users through creating standardized Conventional Commits messages using a structured XML template. It provides instructions for inspecting changes via git diff/status, constructing commit messages with type, scope, description, and optional body/footer fields, and executing the final commit. The skill references the Conventional Commits specification for validation.

Detected Capabilities

git execution (git status, git diff, git add, git commit)file inspection (via git diff)command-line execution

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

write commit messageconventional commitsstandardize commit formatsemantic versioningstructured commit

Referenced Domains

External domains referenced in skill content, detected by static analysis.

www.conventionalcommits.org

Use Cases

Generate well-formatted conventional commit messages
Standardize commit messaging across a team
Create commits that follow semantic versioning conventions
Automatically execute git commits with proper formatting
Learn proper commit message structure and best practices

Quality Notes

Skill clearly explains the Conventional Commits specification with concrete examples (feat, fix, docs, refactor, chore)
XML structure is well-organized and easy to follow, making it simple for users to construct proper commit messages
Includes validation rules for each field, ensuring messages conform to the specification
Step-by-step workflow clearly guides the user from reviewing changes through committing
Referenced domain (www.conventionalcommits.org) provides authoritative specification documentation
No error handling documented for git failures or malformed commit messages
Skill assumes user familiarity with git workflows (staging, diffing); no explanation of git commands provided
Missing guidance on scope selection — users may create inconsistent scope naming across commits
No mention of integration with CI/CD systems that may enforce conventional commit lint rules

Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

conventional-commit