git-commit
SkillProductivityReview and commit the task’s intended changes using repository conventions. Use when the user types /git-commit.
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 git-commit skill
What this skill tells your AI
The instructions your AI receives, as published by blockmatic/basilic in .agents/skills/workflow/git-commit/SKILL.md and read by ahel’s review.
Create short, focused commit message and commit staged changes. Never use --no-verify. Never use --trailer for Co-authored-by or similar. Fix all automated review errors and warnings before committing. Use the default global git user (git config --global user.name, git config --global user.email) for all commits—never cursor/system identity.
- Review changes: Check diff
git diff --cached(staged) orgit diff(unstaged), understand what changed and why - Docs: If behavior, commands, or conventions changed, update matching MDX and nearest README before staging—or one line why they did not change
- Fix errors and warnings: Resolve all lint, type-check, and test failures
- Stage changes (if not already staged):
git add -A - Create short commit message: Follow Conventional Commits. Format:
<type>(<scope>): <short summary>or<issue-key>: <type>(<scope>): <short summary>. Type and scope lowercase (e.g.feat(fastify):). Short summary lowercase, imperative mood (use "fix", "add", "update" not "fixed", "added", "updated"), <= 60 chars, no period. Scope by app (next,fastify,docu), package (ui,core,utils), or omit if general.
Signals
- GitHub stars
- 89
- Forks
- 11
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
git-commit-blockmatic- Source
- github.com/blockmatic/basilic