Agent skill

Conventional Commits

Format commit messages using the Conventional Commits specification.

MITAuto-check passedDevelopment

Install Conventional Commits

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill conventional-commits -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team conventional-commits --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/conventional-commits .claude/skills/conventional-commits && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "conventional-commits" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/conventional-commits into .claude/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/conventional-commits

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill conventional-commits -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team conventional-commits --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/conventional-commits .agents/skills/conventional-commits && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "conventional-commits" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/conventional-commits into .agents/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill conventional-commits -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team conventional-commits --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/conventional-commits .cursor/skills/conventional-commits && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "conventional-commits" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/conventional-commits into .cursor/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/aAAaqwq/AGI-Super-Team.git --path skills/conventional-commits

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill conventional-commits -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team conventional-commits --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/conventional-commits .gemini/skills/conventional-commits && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "conventional-commits" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/conventional-commits into .gemini/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team conventional-commits

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill conventional-commits -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/conventional-commits .github/skills/conventional-commits && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "conventional-commits" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/conventional-commits into .github/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill conventional-commits -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team conventional-commits --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/conventional-commits .opencode/skills/conventional-commits && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "conventional-commits" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/conventional-commits into .opencode/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: conventional-commits
GitHub stars: 105
Used in: 2 other repos
Token cost: ~1.2k tokens
SKILL.md length: 402 words
Files: 3
Skills in repo: 152
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Format commit messages using the Conventional Commits specification.

Works in 3 steps: Using ! in the type/scope → Using BREAKING CHANGE footer → Both methods
Creating commits
SKILL.md covers Format Structure, Commit Types, Scope and Description, plus 7 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Conventional Commits is an agent skill from aAAaqwq/AGI-Super-Team. Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `.clawhub/origin.json` and `_meta.json`).

It sits in Development, covering Commit messages. The repository describes itself as: An installable, cross-framework AI organization: C-suite agents, expert subagents, curated skills, independent review, and one-command setup across 18 AI client/runtime adapters. The licence is MIT.

When your agent uses it

Creating commits
Writing commit messages
The user mentions commits
Commit messages

Example prompts

“/conventional-commits”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Using ! in the type/scope
Using BREAKING CHANGE footer
Both methods

What it can do on your machine

Read from SKILL.md and the folder at commit 331ecd3. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- conventionalcommits.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Conventional Commits loads about 1.2k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 402 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~81
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aAAaqwq/AGI-Super-Team at commit 331ecd3, republished under its MIT licence (© aAAaqwq). 402 words, ~1,241 tokens.

Download SKILL.mdSave it as .claude/skills/conventional-commits/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: conventional-commits
description: Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.
license: MIT
metadata.author: github.com/bastos
metadata.version: 2.0

Conventional Commits

Format all commit messages according to the Conventional Commits specification. This enables automated changelog generation, semantic versioning, and better commit history.

Format Structure

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

Required Types

feat: - A new feature (correlates with MINOR in Semantic Versioning)
fix: - A bug fix (correlates with PATCH in Semantic Versioning)

Common Additional Types

docs: - Documentation only changes
style: - Code style changes (formatting, missing semicolons, etc.)
refactor: - Code refactoring without bug fixes or new features
perf: - Performance improvements
test: - Adding or updating tests
build: - Build system or external dependencies changes
ci: - CI/CD configuration changes
chore: - Other changes that don't modify src or test files
revert: - Reverts a previous commit

Scope

An optional scope provides additional contextual information about the section of the codebase:

feat(parser): add ability to parse arrays
fix(auth): resolve token expiration issue
docs(readme): update installation instructions

Description

Must immediately follow the colon and space after the type/scope
Use imperative mood ("add feature" not "added feature" or "adds feature")
Don't capitalize the first letter
No period at the end
Keep it concise (typically 50-72 characters)

Body

Optional longer description providing additional context
Must begin one blank line after the description
Can consist of multiple paragraphs
Explain the "what" and "why" of the change, not the "how"

Breaking Changes

Breaking changes can be indicated in two ways:

1. Using `!` in the type/scope

feat!: send an email to the customer when a product is shipped
feat(api)!: send an email to the customer when a product is shipped

feat: allow provided config object to extend other configs

BREAKING CHANGE: `extends` key in config file is now used for extending other config files

3. Both methods

chore!: drop support for Node 6

BREAKING CHANGE: use JavaScript features not available in Node 6.

Examples

Simple feature

feat: add user authentication

Feature with scope

feat(auth): add OAuth2 support

Bug fix with body

fix: prevent racing of requests

Introduce a request id and a reference to latest request. Dismiss
incoming responses other than from latest request.

Remove timeouts which were used to mitigate the racing issue but are
obsolete now.

Breaking change

feat!: migrate to new API client

BREAKING CHANGE: The API client interface has changed. All methods now
return Promises instead of using callbacks.

Documentation update

docs: correct spelling of CHANGELOG

Multi-paragraph body with footers

fix: prevent racing of requests

Introduce a request id and a reference to latest request. Dismiss
incoming responses other than from latest request.

Remove timeouts which were used to mitigate the racing issue but are
obsolete now.

Reviewed-by: Z
Refs: #123

Show full SKILL.md (171 more words)Show less

Guidelines

Always use a type - Every commit must start with a type followed by a colon and space
Use imperative mood - Write as if completing the sentence "If applied, this commit will..."
Be specific - The description should clearly communicate what changed
Keep it focused - One logical change per commit
Use scopes when helpful - Scopes help categorize changes within a codebase
Document breaking changes - Always indicate breaking changes clearly

Semantic Versioning Correlation

fix: → PATCH version bump (1.0.0 → 1.0.1)
feat: → MINOR version bump (1.0.0 → 1.1.0)
BREAKING CHANGE → MAJOR version bump (1.0.0 → 2.0.0)

When to Use

Use this format for:

All git commits
Commit message generation
Pull request merge commits
When the user asks about commit messages or git commits

Common Mistakes to Avoid

❌ Added new feature (past tense, capitalized) ✅ feat: add new feature (imperative, lowercase)

❌ fix: bug (too vague) ✅ fix: resolve null pointer exception in user service

❌ feat: add feature (redundant) ✅ feat: add user profile page

❌ feat: Added OAuth support. (past tense, period) ✅ feat: add OAuth support

Files

SKILL.md and 2 other files in skills/conventional-commits of aAAaqwq/AGI-Super-Team.

SKILL.md
.clawhub/origin.json
_meta.json

Open the folder on GitHubat commit 331ecd3

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in aAAaqwq/AGI-Super-Team, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Conventional Commits next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Conventional Commits compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Conventional Commits this skillaAAaqwq/AGI-Super-Team	105	2 repos	~1.2k	Automated safety check: Pass	MIT	11 days ago
Contextual Commit Messagesyamadashy/repomix	29k	1 repos	~2.7k	Automated safety check: Pass	MIT	5 days ago
React Router Release Notes Prepremix-run/react-router	57k	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Caveman Commitvishiri/fantasia-archive	409	13 repos	~642	Automated safety check: Pass	GPL-3.0	today
PR Finalize Reviewmicrosoft/garnet	12k	—	~3.1k	Automated safety check: Pass	MIT	today
ToolJet Multi-Repo CommitToolJet/ToolJet	41k	—	~1.3k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Contextual Commit Messages
yamadashy/repomix
Writes Conventional Commits whose bodies carry action lines recording the intent, decisions and constraints behind a change, not only what changed.
29k GitHub starsUsed in 1 repo~2.7k tokens
DevelopmentAuto-check passed
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
57k GitHub stars~1.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Caveman Commit
vishiri/fantasia-archive
Ultra-compressed commit message generator. An agent skill from vishiri/fantasia-archive.
409 GitHub starsUsed in 13 repos~642 tokens
DevelopmentAuto-check passed
PR Finalize Review
microsoft/garnet
Official
Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.
12k GitHub stars~3.1k tokensUpdated today
DevelopmentAuto-check passed
ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
41k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
103k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes

Questions about Conventional Commits

What does Conventional Commits do?

Format commit messages using the Conventional Commits specification. Conventional Commits is an agent skill from aAAaqwq/AGI-Super-Team. Format commit messages using the Conventional Commits specification.

When should I use Conventional Commits?

Conventional Commits fits situations like: creating commits; writing commit messages; the user mentions commits; commit messages.

How do I install Conventional Commits in Claude Code?

Run `npx skills add aAAaqwq/AGI-Super-Team --skill conventional-commits -a claude-code`. Or copy the skill folder (skills/conventional-commits in aAAaqwq/AGI-Super-Team) into .claude/skills/conventional-commits in your project. Claude Code loads it when a task matches its description.

How do I install Conventional Commits in Codex?

Run `npx skills add aAAaqwq/AGI-Super-Team --skill conventional-commits -a codex`. Or copy the skill folder (skills/conventional-commits in aAAaqwq/AGI-Super-Team) into .agents/skills/conventional-commits in your project. Codex loads it when a task matches its description.

Can I use Conventional Commits in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aAAaqwq/AGI-Super-Team --skill conventional-commits -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conventional-commits, .gemini/skills/conventional-commits, .github/skills/conventional-commits and .opencode/skills/conventional-commits in your project.

What does Conventional Commits need to run?

SKILL.md names no scripts, command-line tools or credentials: Conventional Commits is instructions for the agent only.

Does Conventional Commits access the network?

SKILL.md names 1 domain. As links in the text: conventionalcommits.org. This is read from the text; nothing was executed.

Is Conventional Commits safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Conventional Commits use?

Conventional Commits is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Conventional Commits use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Conventional Commits?

Skills that share tags, products or a category with Conventional Commits: Contextual Commit Messages (yamadashy/repomix, 29k stars), React Router Release Notes Prep (remix-run/react-router, 57k stars), Caveman Commit (vishiri/fantasia-archive, 409 stars) and PR Finalize Review (microsoft/garnet, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Conventional Commits?

aAAaqwq (a GitHub user) maintains it in aAAaqwq/AGI-Super-Team, which has 105 GitHub stars. The repository holds 152 skills in this directory. The repository was last updated on September 27, 2026.

Source: aAAaqwq/AGI-Super-Team on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Conventional Commits

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Conventional Commits

Format Structure

Commit Types

Required Types

Common Additional Types

Scope

Description

Body

Breaking Changes

1. Using ! in the type/scope

2. Using BREAKING CHANGE footer

3. Both methods

Examples

Simple feature

Feature with scope

Bug fix with body

Breaking change

Documentation update

Multi-paragraph body with footers

Guidelines

Semantic Versioning Correlation

When to Use

Common Mistakes to Avoid

Files

Used in 2 other repositories

Compare with similar skills

Similar skills

More from aAAaqwq/AGI-Super-Team

Related

Questions about Conventional Commits

1. Using `!` in the type/scope