/commit

SkillCommunication

Lets your agent write a properly formatted commit message and stage the current code changes.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the /commit skill

About this capability

Stage and create a Conventional Commits message for the current change

What this skill tells your AI

The instructions your AI receives, as published by evermind-ai/everos in .claude/skills/commit/SKILL.md and read by ahel’s review.

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

Run git status and git diff (and git diff --staged) to see what changed.
Review recent history for style: git log --oneline -10.
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.

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>

Never use --no-verify. If pre-commit hooks fail, fix the cause and re-commit.
Do not commit secrets, generated artifacts, or work-in-progress directly to the protected main branch.

Type	Use for
`feat`	new feature
`fix`	bug fix
`refactor`	behavior-preserving restructure
`test`	add / update tests
`docs`	documentation
`style`	formatting only
`perf`	performance
`chore`	config / build / tooling
`build`	build system or dependencies
`ci`	CI configuration
`revert`	revert a previous commit

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.

Advanced