Create conventional commits from staged/unstaged changes. Use when user asks to commit, create commits, commit changes, commit all, make commits, separate commits, commit everything, stage and commit, commit these changes, save and push, commit this work, or requests push after committing. Handles single or multiple commits, staging, message generation from diffs, and push operations.
Stage changes and create conventional commits from diff analysis. Use when user asks to commit, create commits, or push after committing. Handles single/multiple commits, staging, message generation, and push operations.
/plugin marketplace add otrebu/agents/plugin install development-lifecycle@otrebu-dev-toolsThis skill is limited to using the following tools:
Stage changes and create conventional commits from diff analysis.
git status
git diff HEAD
git log --oneline -10
Single commit: All changes relate to one logical change Multiple commits: Changes span distinct features/fixes/areas
If multiple commits needed:
Review diff to extract:
Stage related files:
git add <files-for-this-commit>
Never stage:
.env filesFormat:
<type>(scope): description
Optional body with details
Rules:
Multiple commits: Return to step 3 for next commit
Push requested: Run git push after all commits
No push requested: Stop after committing
feat - New featuresfix - Bug fixesrefactor - Code restructuring without behavior changedocs - Documentation onlytest - Testschore - Tooling, deps, configSingle commit:
feat(api): add user authentication endpoint
Implements JWT token generation, login/logout routes,
and bcrypt password hashing.
Multiple commits scenario:
1. chore(deps): install jsonwebtoken and bcrypt
2. feat(auth): add JWT token signing function
3. feat(auth): add token verification middleware
4. docs(api): document authentication endpoints
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.