Conventional commits

Skill pngdeity/apm-user-repository/packages/development-practices/.apm/skills/conventional-commits

Personal APM marketplace — skills, prompts, agents, and instructions for AI coding agents

Install

npx -y skills add pngdeity/apm-user-repository --skill conventional-commits

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Enforce the Conventional Commits specification for git commit messages. Use when writing commit messages, setting up commit linting, or configuring automated versioning and changelog generation.

SKILL.md

2.8 KB, 543 tokens by cl100k_base, as published. Nobody here has run it

Conventional Commits

Description

Enforces the Conventional Commits specification for all git commit messages within this repository. This standard provides a lightweight convention on top of commit messages, ensuring a clear and machine-readable commit history which facilitates automated versioning and changelog generation.

Instructions

1. Commit Message Format

All commit messages must follow this structural pattern:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

2. Mandatory Types

You must use one of the following types to categorize your changes:

feat: A new feature.
fix: A bug fix.
docs: Documentation only changes.
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc).
refactor: A code change that neither fixes a bug nor adds a feature.
perf: A code change that improves performance.
test: Adding missing tests or correcting existing tests.
build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm).
ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs).
chore: Other changes that don't modify src or test files.
revert: Reverts a previous commit.

3. Guidelines

Subject Line: The subject line must be a succinct description of the change. Use the imperative, present tense: "change" not "changed" nor "changes". Do not capitalize the first letter and do not end with a period.
Scope (Optional): A scope may be provided to a commit's type, to provide additional contextual information and is contained within parenthesis, e.g., feat(parser): add ability to parse arrays.
Breaking Changes: Breaking changes must be indicated by an ! after the type/scope, or by including BREAKING CHANGE: at the beginning of the footer section. A breaking change can be part of a commit of any type.
Body (Optional): Use the body to explain the "what" and "why" of the change, as opposed to the "how".
Footer (Optional): Use the footer to reference GitHub issues that this commit closes or to provide other metadata.

4. Verification

Before finalizing a commit, verify that it adheres to this specification. If using an automated tool or agent to commit, ensure it is configured to follow these rules strictly.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most pr commit review skills give in 543 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07

Use conventional commits formatin 127 of 888, across 115 files
Keep subject line under 72 charactersin 62 of 888, across 48 files
Delete branches after mergein 51 of 888, across 38 files
Use imperative mood in subject linein 51 of 888, across 42 files
Use imperative mood in commit messagesin 44 of 888
Verify directory is ignored before creating worktreein 43 of 888, across 12 files
Generate a conventional commit messagein 43 of 888
Add unignored worktree directories to gitignorein 42 of 888, across 10 files
Make atomic commitsin 39 of 888, across 27 files
Run tests before committingin 36 of 888, across 25 files
Verify clean test baselinein 35 of 888, across 9 files
Split unrelated changes into separate commitsin 35 of 888, across 30 files

Said here and by no other author read

wrap the optional scope in parentheses

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.