agentmods.dev

conventional-commits

conventional-commits is a skill for Claude Code, Codex from whitebeardit/.cursor. It costs 42 tokens per session (2,526 once invoked), scanned A, original, MIT.

A guide and checker for Conventional Commits, a standard way to format commit messages such as “fix: handle timeout.” It also explains how these messages work with semantic-release, a tool that can create software releases from commit history.

In plain words
What is it for?
Use it to write or validate commits, suggest pull-request titles, group changes by type, and understand how a commit may affect the next release.
Why use it?
It removes guesswork from writing commit messages and helps teams keep commits consistent for automated release decisions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 12repo 6mo ago A scan 42 tokens original MIT

Good fit Use it to write or validate commits, suggest pull-request titles, group changes by type, and understand how a commit may affect the next release.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/whitebeardit/.cursor/skill-conventional-commits
View source ↗ whitebeardit/.cursor
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add whitebeardit/.cursor --skill skill-conventional-commits
Clone the repo
git clone --depth 1 https://github.com/whitebeardit/.cursor

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for conventional-commits

README.md
[![agentmods](https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-conventional-commits/github.svg)](https://agentmods.dev/skills/whitebeardit/.cursor/skill-conventional-commits)
Your own site
<a href="https://agentmods.dev/skills/whitebeardit/.cursor/skill-conventional-commits"><img src="https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-conventional-commits/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for conventional-commits

Your own site · 80×15
<a href="https://agentmods.dev/skills/whitebeardit/.cursor/skill-conventional-commits"><img src="https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-conventional-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,526 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.02526
Opus 5 $0.00021 $0.01263
Sonnet 5 $0.00008 $0.00505
Haiku 4.5 $0.00004 $0.00253

Measured 9d ago against content hash 854a45d3e93c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

conventional-commits scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/shared/skill-conventional-commits/SKILL.md · 341 lines

How it starts

The opening of the file, as written. The whole thing — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Conventional Commits

This skill provides the complete specification for Conventional Commits format, validation rules, and integration with semantic-release.

When to Use

✅ DO Use:

  • Creating commit messages
  • Validating commit format
  • Suggesting commit messages
  • Creating PR titles
  • Understanding semantic-release behavior
  • Grouping commits by context

❌ DON'T Use:

  • For release commits (automatically generated by semantic-release)
  • For temporary or debug commits

Commit Format

<type>(<scope>): <subject>

[optional body]

[optional footer(s)]

Commit Types

Allowed Types

  • feat: New feature (generates MINOR version: 1.0.0 → 1.1.0)
  • fix: Bug fix (generates PATCH version: 1.0.0 → 1.0.1)
  • docs: Documentation-only changes (no release by default)
  • style: Formatting changes that don't affect code (no release by default)
  • refactor: Code refactoring without functionality changes (no release by default)
  • perf: Performance improvements (no release by default)
  • test: Adding or fixing tests (no release by default)
  • build: Build system or dependency changes (no release by default)
  • ci: CI/CD configuration changes (no release by default)
  • chore: Other changes that don't fit categories (no release by default)
  • revert: Reverts a previous commit

Type Prioritization

When determining commit type, prioritize in this order:

  1. feat - For new features
  2. fix - For bug fixes
  3. refactor - For refactoring without behavior changes
  4. docs - For documentation changes
  5. test - For adding/fixing tests
  6. chore - For maintenance tasks

Scope

The scope should indicate the affected code area.

When to Use Scope

  • Use scope when the change affects a specific module/component
  • Omit scope when the change affects multiple areas or is general

Common Scopes

Generic examples:

  • domain - Domain entities and business logic
  • service - Service layer
  • api - API endpoints
  • db - Database operations
  • auth - Authentication/authorization
  • utils - Utility functions
  • component - UI components
  • model - Data models
  • controller - Controllers
  • validator - Validation logic

Read the full file on GitHub · 341 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 341 lines · 42 tokens per session scan A 854a45d3e93c

Subscribe to this mod's changes

conventional-commits is a skill published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 2,526 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

CommitsGit and workflow
Related

Other skills, from other repositories

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/orm · 47 tokens

git-commit

Generate well-formatted git commit messages following conventional commit standards.

ThinkInAIXYZ/deepchat · 15 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

contributing

How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…

HugoRCD/evlog · 68 tokens

strict-tdd

Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.

a5c-ai/babysitter · 34 tokens

git-commit

Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…

redai-infra/Relax · 73 tokens