Use when creating git commits. Defines conventional commit format and message structure guidelines.
/plugin marketplace add craigtkhill/stdd-agents/plugin install stdd-agents@stdd-agentsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Guidelines for writing clear, consistent git commit messages.
Use the conventional commits style:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
<type>[optional scope]!: <description>
[optional body]
[optional footer: value]
[optional footer: value]
Add scope in parentheses to provide additional context:
Indicate breaking changes with ! after type/scope:
For complex changes, use a body to provide context:
Footers provide metadata about the commit.
Document breaking changes in footer:
IMPORTANT: Do NOT include AI attribution footers like:
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Keep commit messages clean and focused on the changes themselves.
git fetchgit status and git diffgit add <files>When following the spec-test-driven development workflow:
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.