Commit

Skill vainjs/skills/skills/commit

Mandatory workflow for any task that generates a git commit or commit message. Use this skill whenever the user asks to commit changes, stage and commit, create a commit, or write a Conventional Commits/commitlint message, even if they do not explicitly say "skill".From its SKILL.md

Install

npx -y skills add vainjs/skills --skill commit

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.

SKILL.md

2.2 KB, 501 tokens by cl100k_base, as published. Nobody here has run it

Enforcement

This skill MUST be followed exactly. Steps MUST execute in order. Do not skip, merge, or reorder any step.

Format

<type>(<scope>): <description>
[optional body]
[optional footer(s)]

Types

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

Rules

type: Required, lowercase, from the list above
scope: Optional. Only include when it clearly adds context (e.g. feat(ui): vs feat:). Lowercase, kebab-case if multi-word.
description: Required, lowercase start, no period at end, imperative mood (what the change does, not what it did), max 72 chars
body: Optional, wrap at 100 chars, explain "what" and "why" (not "how")
footer: Optional, for breaking changes (BREAKING CHANGE:) or issue refs (Closes #123, Fixes #456)

Breaking Changes

Append ! to type/scope, or add BREAKING CHANGE: footer.

Examples

feat(auth): add OAuth2 login support
fix(ui): resolve button alignment on mobile
docs: update API documentation
refactor(auth): simplify error handling logic
chore(deps): upgrade React to v19

Workflow — Execute in Exact Order

MANDATORY — Run exactly git add -A. Before confirmation, no other git command is allowed, including git config, git status, git diff, or git log.
MANDATORY — Abort if the commit would use an AI author name/email, AI credentials, Co-Authored-By, or --author with an AI identity.
MANDATORY — Generate the commit message in Conventional Commits format.
MANDATORY — Output the commit message on its own line at the END of your response. Nothing — no explanation, no commentary, no emoji — should follow it:

feat(auth): add OAuth2 login
MANDATORY — Wait for user confirmation. If confirmed, run only the direct git commit command for the generated message. If declined, stop.

What ships with it

Read from the repository

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

Gives 1 of the 12 instructions most pr commit review skills give in 501 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 messagehere, and in 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

execute steps in order
run git add -A first
abort if commit uses an AI identity
place commit message at the end of response

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.