| name | commit |
| description | Create a Conventional Commit message for staged changes and run git commit. Use when changes are staged and you need a commit message in the form type(scope): subject, with a <=100 character imperative header and optional 'ref AL-###' body line. Retained for reference; use only when explicitly asked for this commit workflow. |
Commit — Skill
Retained for reference only. This skill is not part of the active repo routing and should not be used unless a user explicitly asks for this commit workflow.
Name: commit
Purpose: Create a Conventional Commit message for staged changes and run git commit.
Use this skill when you are ready to commit work in this repo.
Applies when: Changes are staged and you need a commit message.
Do not use when: Nothing is staged or you are not using Git.
Rules
- Types:
feat, fix, docs, style, refactor, test, chore, perf, ci, build, revert.
- Header format:
type(scope): subject (scope optional).
- Header max length: 100 characters.
- Subject: imperative, no trailing period, no emojis.
- Issue refs: include
ref AL-### in the body only when applicable.
Workflow
- Confirm something is staged.
- Review staged diff and affected paths.
- Detect relevant
AL-### keys (branch, diff, or recent commits).
- Choose the best commit type and optional scope.
- Write an imperative subject (<= 100 chars).
- Compose the commit message, then run
git commit.
Checklists
Pre-commit checklist
Review checklist
Minimal examples
Commit without body
git commit -m "fix(auth): handle empty session"
Commit with body + issue refs
git commit -m "feat(billing): add invoice export" -m "Add export endpoint and UI action" -m "ref AL-123"
Common mistakes / pitfalls
- Committing with no staged changes
- Using vague subjects ("update stuff")
- Exceeding header length
- Adding
ref AL-### when no issue applies
