Use when generating conventional commit messages from staged git changes. Trigger with phrases like "create commit message", "generate smart commit", "/commit-smart", or "/gc". Automatically analyzes changes to determine commit type (feat, fix, docs), identifies breaking changes, and formats according to conventional commit standards.
/plugin marketplace add jeremylongshore/claude-code-plugins-plus/plugin install git-commit-smart@claude-code-plugins-plusThis skill is limited to using the following tools:
assets/README.mdassets/commit_template.txtassets/example_diff.txtreferences/README.mdscripts/README.mdscripts/commit_analyzer.pyscripts/commit_formatter.pyscripts/git_utils.pyBefore using this skill, ensure:
git addtype(scope): descriptionGenerates conventional commit messages in this format:
type(scope): brief description
- Detailed explanation of changes
- Why the change was necessary
- Impact on existing functionality
BREAKING CHANGE: description if applicable
Examples:
feat(auth): implement JWT authentication middlewarefix(api): resolve null pointer exception in user endpointdocs(readme): update installation instructionsCommon issues and solutions:
No Staged Changes
git add <files> before generating commit messageGit Not Initialized
git init or navigate to repository rootUncommitted Changes
git stash for unrelated modificationsInvalid Commit Format
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.