Generates semantic commit messages from git diff following conventional commits format. Use when user asks to commit changes, wants help writing a commit message, or needs to create a git commit.
Generates semantic commit messages from git diff following conventional commits format. Use when user asks to commit changes, wants help writing a commit message, or needs to create a git commit.
/plugin marketplace add theflysurfer/claude-skills-marketplace/plugin install theflysurfer-claude-skills-marketplace@theflysurfer/claude-skills-marketplaceThis skill is limited to using the following tools:
This skill analyzes git diff and git status to generate a semantic commit message following the project's conventions.
Generates commit messages in this format:
<type>(<scope>): <description>
<body>
š¤ Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
| Type | When to Use |
|---|---|
feat | New feature or functionality |
fix | Bug fix |
docs | Documentation only changes |
refactor | Code refactoring (no functional change) |
style | Formatting, missing semicolons (no code change) |
test | Adding or updating tests |
chore | Maintenance (dependencies, config, etc.) |
| Scope | When to Use |
|---|---|
wordpress | WordPress content, pages, posts, config |
docs | Documentation (docs/ directory) |
design | CSS, design system, visual changes |
infra | Docker, Nginx, VPS, deployment |
a11y | Accessibility improvements |
- prefixgit status
Look for:
# Staged changes
git diff --cached
# Or all changes if nothing staged
git diff
Analyze:
git log --oneline -10
Note:
Changes:
+ docs/wordpress/guides/GUTENBERG_WP_CLI.md (new file)
+ .claude/agents/wordpress-dev.md (new file)
Generated commit:
feat(wordpress): Add WP-CLI guide and wordpress-dev agent
- Created comprehensive WP-CLI guide (250 lines)
- Implemented wordpress-dev subagent for automated page creation
- Added STDIN injection patterns for content updates
- Documented common WP-CLI commands and troubleshooting
š¤ Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Changes:
- .service-card { padding: 20px; }
+ .service-card { padding: var(--space-6); }
Generated commit:
fix(design): Use design tokens for service card padding
Replaced hardcoded 20px with var(--space-6) for consistency
with 8px grid system.
š¤ Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Changes:
+ docs/wordpress/README.md (new file)
~ docs/wordpress/GUIDE_RAPIDE.md (modified)
Generated commit:
docs: Add README navigation and update quick start guide
- Created README.md with documentation structure
- Updated GUIDE_RAPIDE.md with SSH access patterns
- Added cross-references between documents
š¤ Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Changes:
- Duplicated gradient code in 6 files
+ Created _snippets/hero-gradient-violet-orange.php
~ Updated all files to reference snippet
Generated commit:
refactor(docs): Extract hero gradient to DRY snippet
- Created canonical hero-gradient-violet-orange.php snippet
- Removed 6 duplicate gradient implementations
- Updated all documentation to reference snippet
- Improves maintainability and follows DRY principle
š¤ Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Changes:
+ .claude/agents/design-validator.md
+ docs/wordpress/foundations/ACCESSIBILITY_WCAG.md
~ README.md
Generated commit:
feat(a11y): Add design-validator agent and WCAG documentation
- Implemented design-validator subagent for WCAG 2.2 AA compliance
- Created ACCESSIBILITY_WCAG.md foundation document
- Added contrast validation and touch target checking
- Updated README with new agents structure
š¤ Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
# Check what's staged
git status
# See the changes
git diff --cached --stat
# Read the actual diff
git diff --cached
# Check recent commits for style
git log --oneline -5
Ask yourself:
<type>(<scope>): <description max 50 chars>
<body explaining why>
- Bullet point 1
- Bullet point 2
- Bullet point 3
š¤ Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
## Proposed Commit Message
\`\`\`
feat(wordpress): Add new Services page
- Created Services page with 4 service cards
- Used custom-clemence.css classes for styling
- Added hero gradient using canonical snippet
- Validated WCAG AA contrast ratios
š¤ Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
\`\`\`
**Files changed**: 1 insertion
**Type**: New feature
**Scope**: WordPress content
Review this message, then run:
\`\`\`bash
git commit -m "$(cat <<'EOF'
feat(wordpress): Add new Services page
- Created Services page with 4 service cards
- Used custom-clemence.css classes for styling
- Added hero gradient using canonical snippet
- Validated WCAG AA contrast ratios
š¤ Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
\`\`\`
DON'T commit automatically. Always:
git commit commandWarn the user if these files are staged:
.env filescredentials.json.pem, .key)Example warning:
ā ļø **WARNING**: The following files may contain secrets:
- `.env`
- `config/credentials.json`
Are you sure you want to commit these? Consider adding them to .gitignore instead.
Before presenting commit message:
Commit message is successful when:
Use when user says:
Don't use when:
git status clean)git diff directly)Remember: A good commit message explains why the change was necessary, not what changed (the diff shows that). Help the user tell the story of their work.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.