MUST be used for ANY git workflow that involves committing code. This includes explicit commit requests AND implicit ones like 'ship it', 'wrap it up', or finishing implementation work. Handles staging, message generation, validation, and commit execution with conventional commit format.
Validates and executes git commits with conventional format, enforcing message standards and workflow rules.
/plugin marketplace add TechDufus/oh-my-claude/plugin install oh-my-claude@oh-my-claudeThis skill is limited to using the following tools:
scripts/git-commit-helper.shThis skill MUST be invoked whenever you are about to create a git commit. It handles the complete workflow and enforces commit message standards.
Auto-invoke this skill when the user implies code should be committed:
| Category | Trigger Phrases |
|---|---|
| Explicit commit | "commit", "make a commit", "commit this" |
| Ship intent | "ship it", "send it" |
| Finalization | "wrap it up", "finalize this", "we're done", "that's it" |
| After implementation | When you complete work and there are uncommitted changes |
Key insight: If the user's intent results in git commit being run, this skill MUST be used first.
Do NOT run git commit without this skill.
git status # See what's changed
git diff HEAD # See all changes (staged + unstaged)
git log --oneline -5 # Recent commit style reference
Default behavior - stage all changes:
git add -A
If user specifies --staged - skip staging, use only what's already staged.
If user gives instructions - follow them:
Based on the diff, determine:
Message Format:
<type>[optional scope]: <description>
[optional body - explain WHY, not WHAT]
Run the validation script before committing:
${CLAUDE_PLUGIN_ROOT}/skills/git-commit-validator/scripts/git-commit-helper.sh "your commit message here"
The script validates:
Use HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF'
type: description here
EOF
)"
<type>[scope]: <description>| Type | Use For |
|---|---|
feat | New feature or capability |
fix | Bug fix |
docs | Documentation only |
refactor | Code restructuring (no behavior change) |
perf | Performance improvement |
test | Test additions/fixes |
chore | Maintenance, deps |
ci | CI/CD changes |
build | Build system changes |
style | Formatting (no logic change) |
revert | Reverting previous commit |
Simple feature:
feat: add user authentication
Bug fix with scope:
fix(api): resolve timeout on large requests
With body for complex changes:
refactor(auth): simplify token validation
Previous implementation checked tokens in three places.
Consolidated to single middleware for consistency.
Commit messages reflect intent and ownership of the change. AI attribution:
The human owns the commit. The tool is irrelevant.
Note: This skill handles COMMIT only. Push must be requested separately.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.