agentleFS
Sign inStart free
KaryawanSurgaKaryawanSurga/tokensaver-plugin/skills/commitsmith/SKILL.md

commitsmith

Skill1 starsChanged 45 days agoMITView on GitHub

Write conventional commit messages from the staged diff, offline. Use when the user asks to commit work, wants a conventional commit message, or asks what type of change the working tree contains. No API key, no cloud, no diff leaves the machine.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run commitsmith and review the suggestion (type, scope, subject, confidence, evidence).

    line 20
  2. Very specific:

    Commit with --commit, or copy the message.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Commitsmith

Reads the staged diff and suggests a conventional commit — type, scope, subject, body, and breaking-change footer — using local heuristics. This tool is CLI-only inside the family: it reads the repository directly, so there is no MCP server.

Workflow

  1. Stage the intended files with git add.
  2. Run commitsmith and review the suggestion (type, scope, subject, confidence, evidence).
  3. Adjust with --type or --scope when you know better than the heuristics.
  4. Commit with --commit, or copy the message.

CLI

npx -y commitsmith                     # suggest from staged changes
npx -y commitsmith --json              # machine-readable candidates
npx -y commitsmith --type fix --scope parser
npx -y commitsmith --commit            # commit with the top suggestion

Tips

  • New exported API becomes feat; removed exports add ! and a BREAKING CHANGE: footer.
  • Whitespace-only edits become style; deletions-only becomes chore.
  • The tool never commits unless --commit is passed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free