# Conventional Commit > Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation. - Skill: `egohygiene/conventional-commit` (Agent Skill) - Install (CLI): `npx skillmds@latest add egohygiene/conventional-commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/egohygiene/conventional-commit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: egohygiene (https://skillmd.com/u/egohygiene) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/egohygiene/conventional-commit --- ### Instructions ```xml 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. ``` ### Workflow **Follow these steps:** 1. Run `git status` to review changed files. 1. Run `git diff` or `git diff --cached` to inspect changes. 1. Stage your changes with `git add `. 1. Construct your commit message using the following XML structure. 1. After generating your commit message, Copilot will automatically run the following command in your integrated terminal (no confirmation needed): ```bash git commit -m "type(scope): description" ``` 1. Just execute this prompt and Copilot will handle the commit for you in the terminal. ### Commit Message Structure ```xml feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert () A short, imperative summary of the change (optional: more detailed explanation)
(optional: e.g. BREAKING CHANGE: details, or issue references)
 ``` ### Examples ```xml feat(parser): add ability to parse arrays fix(ui): correct button alignment docs: update README with usage instructions refactor: improve performance of data processing chore: update dependencies feat!: send email on registration (BREAKING CHANGE: email service required) ``` ### Validation ```xml Must be one of the allowed types. See https://www.conventionalcommits.org/en/v1.0.0/#specification Optional, but recommended for clarity. Required. Use the imperative mood (e.g., "add", not "added"). Optional. Use for additional context.
Use for breaking changes or issue references.
 ``` ### Final Step ```xml git commit -m "type(scope): description" Replace with your constructed message. Include body and footer if needed. ```