Conventional commits

Skill tuliosousapro/SaaS-blueprint/skills/conventional-commits

Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.From its SKILL.md

Install

npx -y skills add tuliosousapro/SaaS-blueprint --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

4 stars4 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.

SKILL.md

2.4 KB, 566 tokens by cl100k_base, as published. Nobody here has run it

Conventional Commits Skill

When to Use

Every time a git commit is made
When the user asks to "commit this" or "save progress"
When auto-committing after task completion

Reference

Conventional Commits v1.0.0

Instructions

1. Commit Message Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

2. Types

Type	When to Use
`feat`	New feature or capability
`fix`	Bug fix
`docs`	Documentation only changes
`style`	Formatting, missing semicolons, etc. (no code change)
`refactor`	Code change that neither fixes a bug nor adds a feature
`perf`	Performance improvement
`test`	Adding or correcting tests
`build`	Build system or external dependency changes
`ci`	CI configuration changes
`chore`	Other changes that don't modify src or test files

3. Scope (Optional)

Use the BRAINIAC phase or module name:

feat(idea): add competitor analysis playbook
docs(planning): update tech stack playbook
feat(skills): add market-research skill
fix(landing-page): correct CTA link

4. Breaking Changes

Add ! after type/scope for breaking changes:

feat(api)!: change authentication flow to OAuth2

Or use footer:

feat(api): change authentication flow

BREAKING CHANGE: JWT tokens are no longer accepted.

5. Examples

feat(idea): add structured competitor analysis playbook

docs(skills): create market-research skill with Firecrawl integration

fix(landing-page): correct hero section gradient on mobile

chore(tasks): reset todo.md for foundations sprint

refactor(playbooks): rewrite idea phase to match new template

6. Rules

Description: lowercase, imperative mood, no period at end
Max 72 characters for the first line
Body wraps at 100 characters
One logical change per commit
Reference issue numbers in footer when applicable: Refs: #123

Quality Gates

First line matches <type>[scope]: <description> format
Type is from the approved list
Description is imperative mood ("add" not "added", "fix" not "fixed")
No commits with generic messages like "update", "fix stuff", "wip"

What ships with it

Read from the repository

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

Gives 3 of the 12 instructions most pr commit review skills give in 566 tokens

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formathere, and in 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionshere, and in 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactershere, and in 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

Use approved types for commit messages

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.