Commit message

Skill contextosai/skills/skills/commit-message

Write a clear, conventional git commit message from staged changes. Use when the user asks to commit, write a commit message, or describe what changed.From its SKILL.md

Install

npx -y skills add contextosai/skills --skill commit-message

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

2 things to look at

1 stars1 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.
runs commandsInstructs the agent to run 2 commands, including `git diff --staged` and 1 more.

SKILL.md

1.4 KB, 293 tokens by cl100k_base, as published. Nobody here has run it

Commit Message

Generate a high-quality commit message that describes the staged changes.

Steps

Run git diff --staged to see what is actually being committed. If nothing is staged, inspect git status and ask the user what to stage.
Identify the single primary intent of the change. If the diff does more than one unrelated thing, suggest splitting it into multiple commits.
Write the message using the Conventional Commits format.

Format

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

<body — what changed and why, wrapped at ~72 cols>

type: one of feat, fix, refactor, docs, test, chore, perf, build, ci.
subject: imperative mood, lowercase, no trailing period, ≤ 50 chars.
body: optional. Explain why, not just what. Omit for trivial changes.

Guidelines

Describe the effect of the change, not the mechanics of editing files.
Never invent a rationale that isn't supported by the diff.
One logical change per commit.

Examples

feat(auth): add refresh-token rotation

Tokens are now rotated on every refresh so a leaked token is valid for
at most one cycle.

fix(parser): handle empty input without panicking

What ships with it

Read from the repository

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

Gives 2 of the 12 instructions most pr commit review skills give in 293 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 descriptionsin 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjecthere, and in 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 charactersin 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

describe the effect of the change

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.