aif-commit
11
总安装量
10
周安装量
#28084
全站排名
安装命令
npx skills add https://github.com/lee-to/ai-factory --skill aif-commit
Agent 安装分布
opencode
10
gemini-cli
10
claude-code
10
github-copilot
10
codex
10
kimi-cli
10
Skill 文档
Conventional Commit Generator
Generate commit messages following the Conventional Commits specification.
Workflow
-
Analyze Changes
- Run
git statusto see staged files - Run
git diff --cachedto see staged changes - If nothing staged, show warning and suggest staging
- Run
-
Determine Commit Type
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Code style (formatting, semicolons)refactor: Code change that neither fixes a bug nor adds a featureperf: Performance improvementtest: Adding or modifying testsbuild: Build system or dependenciesci: CI configurationchore: Maintenance tasks
-
Identify Scope
- From file paths (e.g.,
src/auth/âauth) - From argument if provided
- Optional – omit if changes span multiple areas
- From file paths (e.g.,
-
Generate Message
- Keep subject line under 72 characters
- Use imperative mood (“add” not “added”)
- Don’t capitalize first letter after type
- No period at end of subject
Format
<type>(<scope>): <subject>
<body>
<footer>
Examples
Simple feature:
feat(auth): add password reset functionality
Bug fix with body:
fix(api): handle null response from payment gateway
The payment API can return null when the gateway times out.
Added null check and retry logic.
Fixes #123
Breaking change:
feat(api)!: change response format for user endpoint
BREAKING CHANGE: user endpoint now returns nested profile object
Behavior
When invoked:
- Check for staged changes
- Analyze the diff content
- Propose a commit message
- Ask for confirmation or modifications
- Execute
git commitwith the message - After a successful commit, offer to push:
- Show branch/ahead status:
git status -sb - If the branch has no upstream, use:
git push -u origin <branch> - Otherwise:
git push - User choice:
- Push now
- Skip push
- Show branch/ahead status:
If argument provided (e.g., /aif-commit auth):
- Use it as the scope
- Or as context for the commit message
Important
- Never commit secrets or credentials
- Review large diffs carefully before committing
- If staged changes contain unrelated work (e.g., a feature + a bugfix, or changes to independent modules), suggest splitting into separate commits:
- Show which files/hunks belong to which commit
- Ask for confirmation
- Unstage all:
git reset HEAD - Stage and commit each group separately using
git add <files>+git commit - Offer to push only after all commits are done
- NEVER add
Co-Authored-Byor any other trailer attributing authorship to the AI. Commits must not contain AI co-author lines