conventional-commit

Use it when:: You want the agent to commit your work with a message in the Conventional Commits format.
It does:: Checks git status and the diff, stages the files, builds a type(scope): description message and runs git commit.
Message:: One of 11 types such as feat, fix, docs or refactor, an optional scope, an imperative summary, and an optional body and footer.
Commits:: Straight away, without asking you to confirm the message.
Unlike git-commit:: That one, from the same repo, first reads your repo's commit rules and makes one commit per logical change; this one applies a fixed template.

Runs git commit as soon as the message is built, without asking you to confirm it.

TL;DR

Conventional Commits is a spec for commit messages that begin with a type, an optional scope and a short summary, like "feat(parser): add ability to parse arrays". The agent runs git status to see what changed, inspects git diff or git diff --cached, and stages files with git add. It builds the message from an XML template: a type from feat, fix, docs, style, refactor, perf, test, build, ci, chore and revert; a scope, optional but recommended; a required summary in the imperative mood ("add", not "added"); an optional body for context; and a footer for breaking changes or issue references, with an example marking a breaking change as feat!. Then it runs git commit -m with the message, with no confirmation step. The skill was written as a Copilot prompt, so its wording has Copilot running the command in your integrated terminal.

Summarizes the skill at 797337f.

npx skills add https://github.com/github/awesome-copilot --skill conventional-commit

skills.sh page Source on GitHub All skills from github/awesome-copilot

Total Downloads: 17,300 on skills.sh, Nov 9, 2026
Repo stars: 40,943 github/awesome-copilot
First seen: Feb 25, 2026 on skills.sh

Weekly Downloads

106

-65% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	307
Sep 28	142
Oct 5	132
Oct 12	113
Oct 19	124
Oct 26	109
Nov 2	91
Nov 9	106

Category	category:engineering category:software-engineering Test-first work, implementation from specs, git hygiene and scope control. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:workflow A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect	effect:local Its own steps create or change files, git state or local tools.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:official A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics	git
Stack	stack:git

SKILL.md

From github/awesome-copilot at 797337f. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: conventional-commit
description: '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.'

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>