CtrlK
BlogDocsLog inGet started
Tessl Logo

commit

Stage and create a Conventional Commits message for the current change

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/commit/SKILL.md
SKILL.md
Quality
Evals
Security

/commit

Create a well-formed commit following the Conventional Commits standard. The format is enforced by gitlint in the commit-msg hook.

Steps

  1. Run git status and git diff (and git diff --staged) to see what changed.

  2. Review recent history for style: git log --oneline -10.

  3. Group the change into a single focused commit. If the working tree mixes unrelated changes, stage selectively (git add -p / specific paths) rather than committing everything at once.

  4. Write the message in Conventional Commits form:

    <type>[(scope)][!]: <imperative summary, ≤72 chars>

<optional body: what & why, wrapped at 72>

<optional footer: BREAKING CHANGE: …, Refs: #123>

  5. Never use --no-verify. If pre-commit hooks fail, fix the cause and re-commit.

  6. Do not commit secrets, generated artifacts, or work-in-progress directly to the protected main branch.

Types

TypeUse for
featnew feature
fixbug fix
refactorbehavior-preserving restructure
testadd / update tests
docsdocumentation
styleformatting only
perfperformance
choreconfig / build / tooling
buildbuild system or dependencies
ciCI configuration
revertrevert a previous commit

Notes

  • No emoji — the title must start with the type.
  • One logical change per commit; keep the history bisectable.
  • The summary is imperative mood: "add", not "added" / "adds".
  • scope is optional: fix(search): …. A ! before the colon (or a BREAKING CHANGE: footer) marks a breaking change.
Repository
EverMind-AI/EverOS
Path

.claude/skills/commit/SKILL.md

Commit

6ff07ef

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill