Agent skill

Conventional Commit

by teddytennant in teddytennant/wizard

Write a conventional commit subject and body from the current diff.

Apache-2.0Auto-check passedDevelopment

Install Conventional Commit

skills CLI
$ npx skills add teddytennant/wizard --skill conventional-commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install teddytennant/wizard conventional-commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/teddytennant/wizard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/registry/skills/teddytennant/conventional-commit .claude/skills/conventional-commit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
conventional-commit
GitHub stars
103
Token cost
~501 tokens
SKILL.md length
296 words
Files
2
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Write a conventional commit subject and body from the current diff.

  • Works in 3 steps: git_status, then git_diff. Prefer the… → The repo's own commit style: git log -15… → Do not invent files you have not seen.…
  • Tasks that involve Commit messages
  • SKILL.md covers What to look at, Subject, Body and Footers, plus 1 more section
  • Calls git

What it does

Conventional Commit is an agent skill from teddytennant/wizard. Write a conventional commit subject and body from the current diff. One change per commit. Do not invent a scope.

Its SKILL.md is about 500 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

It sits in Development, covering Commit messages. It works with Git. The repository describes itself as: The fastest agent in your terminal: one Rust binary, any model. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Commit messages

Example prompts

  • “/conventional-commit”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. git_status, then git_diff. Prefer the staged diff. If nothing is staged, use the unstaged work and say so.
  2. The repo's own commit style: git log -15 --oneline on this branch. Match its type vocabulary and whether it uses scopes.
  3. Do not invent files you have not seen. If the diff is empty, say so and stop.

What it can do on your machine

Read from SKILL.md and the folder at commit 9d123be. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Conventional Commit loads about 501 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 296 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~501

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from teddytennant/wizard at commit 9d123be, republished under its Apache-2.0 licence (© teddytennant). 296 words, ~501 tokens.

Download SKILL.mdSave it as .claude/skills/conventional-commit/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
conventional-commit
description
Write a conventional commit subject and body from the current diff. One change per commit. Do not invent a scope.

Conventional commits

Write the commit message. Do not run git commit unless the user asked.

What to look at

  1. git_status, then git_diff. Prefer the staged diff. If nothing is staged, use the unstaged work and say so.
  2. The repo's own commit style: git log -15 --oneline on this branch. Match its type vocabulary and whether it uses scopes.
  3. Do not invent files you have not seen. If the diff is empty, say so and stop.

Subject

<type>(<optional scope>): <imperative summary>

Default types, unless the repo's history or CONTRIBUTING names others: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert.

  • Imperative, present tense: "add", not "added" or "adds".
  • Aim for 50 characters; 72 is the hard stop.
  • No trailing period, no issue numbers in the subject.
  • Scope is a real area of this tree (registry, gateway, tui), not a mood (misc, stuff, update). Omit the scope rather than guessing.
  • A breaking change gets ! after the type or scope (feat(api)!: drop the old flag) and a BREAKING CHANGE: footer. Size is not a break.

Body

Only when the subject cannot carry the why. Wrap at 72. Explain the reason; the diff already shows the edit. No "this commit", no changelog padding, no marketing.

Footers

  • BREAKING CHANGE: <what a caller must do now> when a public contract changes.
  • Refs: #123 / Closes: #123 only when the user named the issue. Do not scrape numbers out of branch names.

Split

One logical change per commit. If the diff mixes a fix and a refactor, say so and propose the split. Do not write one message that pretends they are one change.

If the user also wants the commit created, use the project's existing commit path (their hook, git commit, the repo's helper). Do not skip hooks unless they said to.

© teddytennant, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in registry/skills/teddytennant/conventional-commit of teddytennant/wizard.

  • SKILL.md
  • manifest.toml

Open the folder on GitHubat commit 9d123be

Compare with similar skills

Conventional Commit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Conventional Commit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Conventional Commit this skillteddytennant/wizard103—~501Automated safety check: PassApache-2.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated today
    DevelopmentAuto-check passed

More from teddytennant/wizard

  • Plain Writing

    teddytennant/wizard

    Write prose that reads like a person wrote it, not a model. An agent skill from teddytennant/wizard.

    103 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Evolve

    teddytennant/wizard

    How to extend Wizard via /evolve. An agent skill from teddytennant/wizard.

    103 GitHub stars~835 tokensUpdated today
    Auto-check passed
  • PR Description

    teddytennant/wizard

    Write a pull-request title and body from the current branch against its base.

    103 GitHub stars~484 tokensUpdated today
    Auto-check passed
  • Undercover

    teddytennant/wizard

    Keep git history clean in public repos. An agent skill from teddytennant/wizard.

    103 GitHub stars~335 tokensUpdated today
    Auto-check passed
  • Coding

    teddytennant/wizard

    Baseline coding workflow. An agent skill from teddytennant/wizard.

    103 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Conventional Commit

What does Conventional Commit do?

Write a conventional commit subject and body from the current diff. Conventional Commit is an agent skill from teddytennant/wizard. Write a conventional commit subject and body from the current diff.

When should I use Conventional Commit?

Conventional Commit fits situations like: tasks that involve Commit messages.

How do I install Conventional Commit in Claude Code?

Run `npx skills add teddytennant/wizard --skill conventional-commit -a claude-code`. Or copy the skill folder (registry/skills/teddytennant/conventional-commit in teddytennant/wizard) into .claude/skills/conventional-commit in your project. Claude Code loads it when a task matches its description.

How do I install Conventional Commit in Codex?

Run `npx skills add teddytennant/wizard --skill conventional-commit -a codex`. Or copy the skill folder (registry/skills/teddytennant/conventional-commit in teddytennant/wizard) into .agents/skills/conventional-commit in your project. Codex loads it when a task matches its description.

Can I use Conventional Commit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add teddytennant/wizard --skill conventional-commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conventional-commit, .gemini/skills/conventional-commit, .github/skills/conventional-commit and .opencode/skills/conventional-commit in your project.

What does Conventional Commit need to run?

Going by SKILL.md and its folder, Conventional Commit needs the command-line tools its instructions call (git).

Does Conventional Commit access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Conventional Commit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Conventional Commit use?

Conventional Commit is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Conventional Commit use?

About 501 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Conventional Commit?

Skills that share tags, products or a category with Conventional Commit: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Conventional Commit?

teddytennant (a GitHub user) maintains it in teddytennant/wizard, which has 103 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.

Source: teddytennant/wizard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.