Create a Conventional Commit
SkillDev toolsCreate conventional commits. Use when: committing staged changes. Triggers on: '/commit', 'conventional 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 Create a Conventional Commit skill
What this skill tells your AI
The instructions your AI receives, as published by ahonn/dotfiles in .claude/skills/commit/SKILL.md and read by ahel’s review.
I'll help you create a commit following the Conventional Commits 1.0.0 specification.
Checking current changes
!git status --short
!git diff --cached --stat
Analyzing changes
Based on the changes, I'll create a commit message following this structure:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Conventional Commit Types
- feat: A new feature (correlates with MINOR in SemVer)
- fix: A bug fix (correlates with PATCH in SemVer)
- docs: Documentation only changes
- style: Changes that don't affect code meaning (white-space, formatting, etc)
- refactor: Code change that neither fixes a bug nor adds a feature
- perf: Code change that improves performance
- test: Adding or correcting tests
- build: Changes to build system or dependencies
- ci: Changes to CI configuration files and scripts
- chore: Other changes that don't modify src or test files
- revert: Reverts a previous commit
Breaking Changes
- Add ! after type/scope for breaking changes (e.g., feat!: or feat(api)!:)
- OR include BREAKING CHANGE: in the footer
Creating the commit
IMPORTANT: This command will NEVER execute git add. It only creates commits from already staged changes.
Based on the staged changes and any specific requirements in "$ARGUMENTS", I'll:
- Determine the appropriate commit type
- Identify if a scope is needed
- Write a clear, concise description
- Add body details if the changes are complex
- Include any necessary footers (BREAKING CHANGE, Refs, etc.)
Then execute the commit with:
git commit -m "$(cat <<'EOF'
[generated commit message here]
EOF
)"
Important: The commit message will be clean and professional, containing:
- The conventional commit format (type, scope, description)
- Optional body and footer as needed
The commit will follow all Conventional Commits 1.0.0 rules:
- Type prefix is required
- Description immediately follows colon and space
- Body (if included) starts one blank line after description
- Footer (if included) starts one blank line after body
- Breaking changes are clearly indicated
Signals
- GitHub stars
- 62
- Forks
- 2
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
commit-ahonn- Source
- github.com/ahonn/dotfiles