Bruno-Cunha-Souza/ValarMindSkills / skills/github-commit
github-commit
UnverifiedGenerate Conventional Commit from staged diff. Triggers: 'commit', 'create commit', 'commit message'.
Conventional Commit
Goal
Analyze staged changes and generate a commit message following the Conventional Commits specification, adapted to project conventions when they exist.
Inputs you must collect before starting
| Input | Required | How to obtain |
|---|---|---|
| Staged changes | Yes | git diff --staged |
| Project conventions | No | Check commitlint config, CLAUDE.md, CONTRIBUTING.md |
| Type, scope, or intent | No | Ask the user if not clear from the diff |
Procedure
Step 1 — Check staged changes
Run git diff --staged. If empty, inform the user there are no staged changes and offer help with git add.
Step 2 — Summary of changed files
Run git diff --staged --stat for a summary of modified, added, or removed files.
Step 3 — Check project conventions
Look for project-specific commit configurations:
.commitlintrc,.commitlintrc.json,.commitlintrc.yml,commitlint.config.js,commitlint.config.tscommitlintsection inpackage.jsonCONTRIBUTING.md,CLAUDE.md- Recent commit history:
git log --oneline -5
If found, project conventions take precedence over default rules.
Step 4 — Analyze the diff
Read the full diff and identify:
- What was added, removed, or modified
- The intent behind the changes (new feature, bug fix, refactor, etc.)
- Which areas of the codebase were affected
Step 5 — Determine the commit type
Choose the appropriate type:
| Type | When to use |
|---|---|
feat | New feature for the user |
fix | Bug fix |
refactor | Code restructuring without changing behavior |
perf | Performance improvement |
style | Formatting, whitespace, semicolons (no logic change) |
test | Adding or fixing tests |
docs | Documentation only |
build | Build system, external dependencies |
ci | CI/CD configuration |
chore | Maintenance tasks that don't fit other types |
Step 6 — Determine the scope (optional)
Identify scope from the area of the codebase affected. Examples: auth, api, ui, db, config. Use scope only if it adds clarity.
Step 7 — Compose the message
Format:
<type>(<scope>): <description>
<optional body>
<optional footer>
Description (subject line) rules:
- Maximum 72 characters
- Imperative mood ("add", not "added" or "adds")
- Lowercase first letter
- No period at the end
Body rules (only when needed):
- Default to no body. Most commits should be subject-only. Add a body only if the "why" is non-obvious from subject + diff (hidden constraint, surprising trade-off, non-local consequence).
- Hard cap: ≤ 4 lines, ≤ 300 characters total, single paragraph. If you need more, split into multiple commits.
- Wrap at 72 characters, separated from the description by a blank line.
- Explain the "why", not the "what". The diff already shows what changed — do not narrate it.
- Forbidden patterns: per-file or per-section enumeration ("Three changes:", "- File A now does X", "- File B now does Y"); restating the subject in prose; describing code structure ("the function now branches on..."); meta-commentary ("Result:", "Confirma?"); trailing questions.
- Bullets allowed only when listing 3+ genuinely independent concerns that share one "why". If you can write one sentence instead, do.
Footer rules (when applicable):
BREAKING CHANGE: <description>for backward-incompatible changesRefs: #<number>to reference issues or PRs
Step 8 — Present and confirm
- Present the message in a code block
- Wait for user approval
- After approval, execute
git commitwith the message
Constraints
- Follow the Conventional Commits spec strictly
- Never invent changes — only describe what the diff shows
- Subject line must be at most 72 characters, imperative mood, lowercase, no period
- Default to subject-only. A body is the exception, not the rule. When unsure, omit it.
- Body, if present, must be ≤ 4 lines and ≤ 350 characters, wrap at 72, separated by a blank line
- Never enumerate files or sections in the body — the diff is the enumeration
- Never end the body with a question or confirmation prompt; the confirmation lives outside the message
- Project conventions take precedence
- Include
BREAKING CHANGE:in the footer when the change breaks backward compatibility - Reference issues/PRs in the footer when the user mentions them
- Never commit without explicit user approval
- Never include the AI agent (Claude, Codex, etc.) in the commit message
- Never include co-authorship in the commit message
Output format
Present the commit message in a code block followed by a confirmation prompt. See examples in EXAMPLE.md.
Example request
- "Commit my changes"
- "Create a commit for the login fix"
- "Commit these changes as a feat"
- "Commit with scope api"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |