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.
Guide for writing conventional commit messages. An agent skill from axone-protocol/contracts.
Install Conventional Commits
$ npx skills add axone-protocol/contracts --skill conventional-commits -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install axone-protocol/contracts conventional-commits --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/conventional-commits .claude/skills/conventional-commits && rm -rf skills-srcUse ~/.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/
Install the "conventional-commits" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/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 install https://github.com/axone-protocol/contracts/tree/main/.agents/skills/conventional-commitsType 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.
$ npx skills add axone-protocol/contracts --skill conventional-commits -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install axone-protocol/contracts conventional-commits --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/conventional-commits .agents/skills/conventional-commits && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "conventional-commits" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/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.
$ npx skills add axone-protocol/contracts --skill conventional-commits -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install axone-protocol/contracts conventional-commits --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/conventional-commits .cursor/skills/conventional-commits && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "conventional-commits" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/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 https://github.com/axone-protocol/contracts.git --path .agents/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.
$ npx skills add axone-protocol/contracts --skill conventional-commits -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install axone-protocol/contracts conventional-commits --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/conventional-commits .gemini/skills/conventional-commits && rm -rf skills-srcUse ~/.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/
Install the "conventional-commits" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/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.
$ gh skill install axone-protocol/contracts conventional-commitsInstalls 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).
$ npx skills add axone-protocol/contracts --skill conventional-commits -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/conventional-commits .github/skills/conventional-commits && rm -rf skills-srcUse ~/.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/
Install the "conventional-commits" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/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.
$ npx skills add axone-protocol/contracts --skill conventional-commits -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install axone-protocol/contracts conventional-commits --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/conventional-commits .opencode/skills/conventional-commits && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "conventional-commits" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/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
- 123
- Token cost
- ~909 tokens
- SKILL.md length
- 309 words
- Files
- 2 (incl. references)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Guide for writing conventional commit messages. An agent skill from axone-protocol/contracts.
- Committing changes
- SKILL.md covers Commit Message Format, Subject Line Rules, Verb Selection and Type, plus 6 more sections
- Calls npm
- Writing commit messages
What it does
Conventional Commits is an agent skill from axone-protocol/contracts. Guide for writing conventional commit messages. Use when committing changes, writing commit messages, or reviewing commit history.
Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/examples.md`).
It sits in Development, covering Commit messages. The repository describes itself as: 📜 Smart contracts for the Axone protocol. The licence is BSD-3-Clause.
When your agent uses it
- Committing changes
- Writing commit messages
- Reviewing commit history
Example prompts
- “/conventional-commits”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 02724f3. 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
Shell commands in SKILL.md call:
npm
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):
commitlint.js.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 909 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 38 tokens; SKILL.md has 309 words of instructions outside code blocks.
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 axone-protocol/contracts at commit 02724f3, republished under its BSD-3-Clause licence (© axone-protocol). 309 words, ~909 tokens.
Download SKILL.mdSave it as
.claude/skills/conventional-commits/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- conventional-commits
- description
- Guide for writing conventional commit messages. Use when committing changes, writing commit messages, or reviewing commit history.
- license
- BSD-3-Clause
- metadata.author
- axone.xyz
- metadata.version
- 1.0
Conventional Commits
Commit Message Format
<type>(<scope>): <verb> <subject>One line only. No body. No footer (except for breaking changes).
Subject Line Rules
- Imperative mood, present tense
- Short, dense, unambiguous
- Describes the intent, not the implementation
- One line only
- No capitalization at start
- No period at end
Verb Selection
⚠️ Avoid weak verbs:
add,remove,change,update,modify
Use precise, action-oriented verbs:
| Verb | Use When |
|---|---|
enforce | Adding constraints or rules |
introduce | Bringing in new concepts/APIs |
implement | Building out functionality |
prevent | Blocking undesired behavior |
fix | Correcting bugs |
refactor | Restructuring without behavior change |
clarify | Improving readability/naming |
align | Making consistent with standards |
tighten | Strengthening validation/constraints |
harden | Security or robustness improvements |
validate | Input/state verification |
handle | Managing edge cases |
support | Enabling new use cases |
ensure | Guaranteeing invariants |
document | Documentation work |
Type
| Type | Description | Triggers |
|---|---|---|
feat | New feature | Minor version bump |
fix | Bug fix | Patch version bump |
docs | Documentation only | No release |
style | Formatting, whitespace | No release |
refactor | Code restructuring | No release |
perf | Performance improvement | Patch version bump |
test | Adding/updating tests | No release |
build | Build system, dependencies | No release |
ci | CI/CD configuration | No release |
chore | Maintenance tasks | No release |
Scope
- Mandatory when it adds clarity
- Short, meaningful, domain or component oriented
- Use contract names without
axone-prefix:gov,logic - Other examples:
workflow,dependabot,README,make,deps - If unsure, omit it
Examples
See examples for comprehensive good and bad examples.
Quick reference:
feat(gov): introduce quadratic voting mechanism
fix(handlers): prevent overflow in vote counting
refactor(state): clarify storage key naming
test(gov): validate error paths for unauthorized access
build(deps): enforce abstract-sdk 0.26.1Granularity
Rule: One commit = one intention
| Instead of... | Prefer... |
|---|---|
| One big mixed commit | Multiple focused commits |
feat: implement X and fix Y | Two separate commits |
| Tests bundled with feature | Separate test: commit |
| Build changes with feature | Separate build: commit |
What to Avoid
- ❌ Generic messages hiding what changed
- ❌ Explanations or rationale in the message
- ❌ Marketing language or inflated wording
- ❌ Multiple intentions in one commit
- ❌ Vague subjects like "improve", "update", "fix issue"
Breaking Changes
Use ! after type/scope:
feat(msg)!: restructure ExecuteMsg variants
refactor(api)!: enforce stricter validation schemaCommit Linting
Commits are validated using commitlint. Ensuring lint passes is mandatory.
Validate locally:
npm i -g @commitlint/cli @commitlint/config-conventional
echo "feat(gov): introduce voting mechanism" | commitlint --extends @commitlint/config-conventional© axone-protocol, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .agents/skills/conventional-commits of axone-protocol/contracts.
- SKILL.md
- references/examples.md
Open the folder on GitHubat commit 02724f3
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Conventional Commits this skillaxone-protocol/contracts | 123 | — | ~909 | Automated safety check: Pass | BSD-3-Clause | |
| Contextual Commit Messagesyamadashy/repomix | 29k | 1 repos | ~2.7k | Automated safety check: Pass | MIT | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Caveman Commitvishiri/fantasia-archive | 409 | 13 repos | ~642 | Automated safety check: Pass | GPL-3.0 | |
| PR Finalize Reviewmicrosoft/garnet | 12k | — | ~3.1k | Automated safety check: Pass | MIT | |
| ToolJet Multi-Repo CommitToolJet/ToolJet | 41k | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
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.
Caveman Commit
vishiri/fantasia-archive
Ultra-compressed commit message generator. An agent skill from vishiri/fantasia-archive.
- Official
PR Finalize Review
microsoft/garnet
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.
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.
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.
More from axone-protocol/contracts
All 9 skills in this repoRust Testing
axone-protocol/contracts
Patterns for Rust testing in Axone CosmWasm contracts. An agent skill from axone-protocol/contracts.
Rust Quality Gates
axone-protocol/contracts
Repository quality gates for Rust and generated artifacts. An agent skill from axone-protocol/contracts.
API Design
axone-protocol/contracts
Best practices for designing CosmWasm smart contract APIs. An agent skill from axone-protocol/contracts.
API Doc Comments
axone-protocol/contracts
Guide for writing Rust doc comments that produce accurate generated contract documentation.
Cosmwasm Contract
axone-protocol/contracts
Axone contract structure and Abstract SDK patterns. An agent skill from axone-protocol/contracts.
Deployment
axone-protocol/contracts
Axone deployment workflows with cargo-make, cw-orch, and Abstract.
Related
Categories
Questions about Conventional Commits
What does Conventional Commits do?
Guide for writing conventional commit messages. An agent skill from axone-protocol/contracts. Conventional Commits is an agent skill from axone-protocol/contracts. Guide for writing conventional commit messages.
When should I use Conventional Commits?
Conventional Commits fits situations like: committing changes; writing commit messages; reviewing commit history.
How do I install Conventional Commits in Claude Code?
Run `npx skills add axone-protocol/contracts --skill conventional-commits -a claude-code`. Or copy the skill folder (.agents/skills/conventional-commits in axone-protocol/contracts) 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 axone-protocol/contracts --skill conventional-commits -a codex`. Or copy the skill folder (.agents/skills/conventional-commits in axone-protocol/contracts) 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 axone-protocol/contracts --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?
Going by SKILL.md and its folder, Conventional Commits needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
Does Conventional Commits access the network?
SKILL.md names 1 domain. As links in the text: commitlint.js.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 BSD-3-Clause 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 909 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 408 tokens, read only when the agent opens those files.
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?
axone-protocol (a GitHub organization) maintains it in axone-protocol/contracts, which has 123 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on September 25, 2026.
Source: axone-protocol/contracts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.