Automatically invoked when user requests git commit message creation, commit drafting, or needs help with conventional commit formatting. Handles conventional commit standards.
Automatically generates conventional commit messages when you request git commits. It analyzes staged changes, drafts messages following standards, and handles commits based on complexity—autonomous for simple fixes, requesting confirmation for features, and requiring approval for breaking changes.
/plugin marketplace add shrwnsan/vibekit-claude-plugins/plugin install base@vibekitThis skill is limited to using the following tools:
examples.mdpatterns.mdscripts/analyze_changes.shscripts/check_attribution.shscripts/validate_commit.shtroubleshooting.mdvalidation.mdA professional git commit message drafting service that follows modern conventional commit standards, provides collaborative attribution, and includes quality validation for reliable development workflows.
This skill follows the principle of progressive disclosure. This file contains the core workflow and high-level guidance. For more detailed information, please refer to the linked reference files.
fix, docs, style, and chore. I can execute these autonomously.feat, refactor, and perf. I will ask for your confirmation before proceeding.git statusgit diff --stagedgit log --oneline -5For detailed information, please refer to these files:
This skill includes executable scripts for validation and analysis.
scripts/validate_commit.sh: Checks if a commit message follows the conventional commit format.scripts/check_attribution.sh: Validates the Co-Authored-By format in a commit message.scripts/analyze_changes.sh: Provides a summary of staged changes to help draft a commit message.ls, grep, etc.)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 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 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.