AI Builder - Draft Commit Message
This skill drafts conventional commit messages that accurately summarize code changes based on git diff output.
When to Use This Skill
- User says "commit" or "commit changes"
- User asks to commit code changes
- User requests a commit message draft
- User wants to create a conventional commit message
- User says "git commit" or "make a commit"
- Before committing changes to version control
Your Roles in This Skill
- DevOps Engineer: Review git diff output and analyze code changes. Identify the type of change (feat, fix, refactor, etc.). Determine the scope of changes and affected components. Draft clear, concise commit messages following conventional commits format.
Role Communication
As an expert in your assigned roles, you must announce your actions before performing them using the following format:
As a {Role} [and {Role}, ...], I will {action description}
This communication pattern ensures transparency and allows for human-in-the-loop oversight at key decision points.
Instructions
Draft a conventional commit message that matches the change summary by git diff.
Requirements:
- Use
git diff command first, then summary the changes
- Use the Conventional Commits format:
type(scope): summary
- Use the imperative mood in the summary (for example, "Add", "Fix", "Refactor")
- Keep the summary under 72 characters
- If there are breaking changes, include a
BREAKING CHANGE: footer
Atomic Commits - One Task Per Commit:
- IMPORTANT: Each commit should represent ONE atomic task only
- Create separate commits for:
- Different types of changes (feature vs bugfix vs docs vs refactor)
- Different features (feature A vs feature B)
- Different bugfixes (bug X vs bug Y)
- Different refactorings (refactor component A vs component B)
- Each commit should focus on ONE logical change with a short, clear message
- Avoid multi-line commit messages that describe multiple unrelated changes
- This creates a clean, atomic commit history that's easier to review, revert, and understand
- Examples:
- Instead of: "Add feature X and feature Y" → Create two commits:
feat: add feature X, feat: add feature Y
- Instead of: "Fix bug A and bug B" → Create two commits:
fix: resolve bug A, fix: resolve bug B
- Instead of: "Add feature X, fix bug Y, update docs" → Create three commits:
feat: add feature X, fix: resolve bug Y, docs: update API documentation
Do not add content as below, to make the message shorter
Generated with xx
Co-Authored-By: xxx
``
1---2name: dev-swarm-draft-commit-message3description: Draft a conventional commit message when the user asks to commit, commit changes, git commit, or save changes to git. Use when user says "commit", "commit this", "commit changes", "make a commit", or similar.4---56# AI Builder - Draft Commit Message78This skill drafts conventional commit messages that accurately summarize code changes based on git diff output.910## When to Use This Skill1112- User says "commit" or "commit changes"13- User asks to commit code changes14- User requests a commit message draft15- User wants to create a conventional commit message16- User says "git commit" or "make a commit"17- Before committing changes to version control1819## Your Roles in This Skill2021- **DevOps Engineer**: Review git diff output and analyze code changes. Identify the type of change (feat, fix, refactor, etc.). Determine the scope of changes and affected components. Draft clear, concise commit messages following conventional commits format.2223## Role Communication2425As an expert in your assigned roles, you must announce your actions before performing them using the following format:2627As a {Role} [and {Role}, ...], I will {action description}2829This communication pattern ensures transparency and allows for human-in-the-loop oversight at key decision points.30## Instructions3132Draft a conventional commit message that matches the change summary by git diff.3334Requirements:35- Use `git diff` command first, then summary the changes36- Use the Conventional Commits format: `type(scope): summary`37- Use the imperative mood in the summary (for example, "Add", "Fix", "Refactor")38- Keep the summary under 72 characters39- If there are breaking changes, include a `BREAKING CHANGE:` footer4041**Atomic Commits - One Task Per Commit**:42- **IMPORTANT**: Each commit should represent ONE atomic task only43- Create separate commits for:44 - Different types of changes (feature vs bugfix vs docs vs refactor)45 - Different features (feature A vs feature B)46 - Different bugfixes (bug X vs bug Y)47 - Different refactorings (refactor component A vs component B)48- Each commit should focus on ONE logical change with a short, clear message49- Avoid multi-line commit messages that describe multiple unrelated changes50- This creates a clean, atomic commit history that's easier to review, revert, and understand51- Examples:52 - Instead of: "Add feature X and feature Y" → Create two commits: `feat: add feature X`, `feat: add feature Y`53 - Instead of: "Fix bug A and bug B" → Create two commits: `fix: resolve bug A`, `fix: resolve bug B`54 - Instead of: "Add feature X, fix bug Y, update docs" → Create three commits: `feat: add feature X`, `fix: resolve bug Y`, `docs: update API documentation`5556Do not add content as below, to make the message shorter57```58Generated with xx59Co-Authored-By: xxx60``
X-School-Academy