skillist-io Git Commit
Use when preparing commits or summarizing a changeset for version control.
When to activate
- User asks to commit changes
- Reviewing staged diff before commit
- Splitting a large diff into logical commits
Procedure
- Read the full diff; identify distinct logical changes.
- Use conventional commits:
feat:,fix:,refactor:,docs:,test:,chore:. - Subject line ≤ 72 chars; body explains why, not just what.
- One concern per commit; avoid mixing unrelated files.
- Never commit secrets,
.env, or credentials.
Output format
feat(scope): short subject
Optional body explaining motivation and trade-offs.