conventional-commit

github/awesome-copilot · updated Apr 8, 2026

$npx skills add https://github.com/github/awesome-copilot --skill conventional-commit
0 commentsdiscussion
summary

Structured prompt template for generating standardized conventional commit messages.

  • Provides XML-formatted workflow guiding users through staging changes, inspecting diffs, and constructing commits with type, scope, description, body, and footer fields
  • Includes validation rules enforcing Conventional Commits specification compliance, with allowed types (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert)
  • Offers six practical examples covering common commit patter
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:

  1. Run git status to review changed files.
  2. Run git diff or git diff --cached to inspect changes.
  3. Stage your changes with git add <file>.
  4. Construct your commit message using the following XML structure.
  5. 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"
  1. 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>

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.528 reviews
  • Benjamin Martin· Dec 28, 2024

    conventional-commit has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Sakshi Patil· Nov 23, 2024

    Keeps context tight: conventional-commit is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Ava Ramirez· Nov 19, 2024

    Solid pick for teams standardizing on skills: conventional-commit is focused, and the summary matches what you get after install.

  • Chaitanya Patil· Oct 14, 2024

    We added conventional-commit from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Amelia Thomas· Oct 10, 2024

    I recommend conventional-commit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Daniel Sharma· Sep 17, 2024

    Useful defaults in conventional-commit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Oshnikdeep· Sep 1, 2024

    Solid pick for teams standardizing on skills: conventional-commit is focused, and the summary matches what you get after install.

  • Daniel Shah· Sep 1, 2024

    conventional-commit has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ganesh Mohane· Aug 20, 2024

    I recommend conventional-commit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Ava Sanchez· Aug 20, 2024

    conventional-commit fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 28

1 / 3