agentleFS
ghvinashvilighvinashvili/specagent/.claude/skills/commit-style/SKILL.md

commit-style

Skill7 starsChanged 13 days agoApache-2.0View on GitHub

Write a Conventional Commits message for the staged changes and commit. Use when Claude is about to commit.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Commit style

  1. git status --short and git diff --cached --stat.
  2. Header <type>(<scope>): <description>: type from feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert; scope = package or area; description in the imperative, at most 72 characters.
  3. Body: what and why, not how. Footer: BREAKING CHANGE: <text> when applicable; Refs: <spec or ADR>.
  4. git commit -m "<header>" -m "<body>". Commitizen's commit-msg stage rejects a header that does not match, where the project installed it (.pre-commit-config.yaml).

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.