Create or switch to feature branches with proper naming conventions. Use when user wants to start working on a new feature, start a feature. Generates feature/branch-name patterns from descriptions, checks existence, and creates/switches accordingly.
Creates or switches to feature branches with proper naming conventions. Use when starting work on a new feature by analyzing descriptions to generate `feature/<slug>` branch names, checking existence, and creating or switching accordingly.
/plugin marketplace add otrebu/agents/plugin install development-lifecycle@otrebu-dev-toolsThis skill is limited to using the following tools:
Creates or switches to feature branches following the feature/<slug> naming convention. Analyzes feature descriptions to generate concise, descriptive branch names and handles branch creation or switching automatically.
Extract 2-4 key words that capture the essence of the feature from the description.
Branch naming rules:
feature/<slug>Examples:
feature/user-authfeature/dark-modefeature/table-paginationfeature/api-refactorBefore creating or switching branches, verify current git status:
git status
Ensure working directory is clean or changes are properly handled.
git branch --show-current
Is it already a feature branch? If so ask the user if they want to branch off from here or go back to main branch first.
Check if the branch already exists:
git branch --list feature/<slug>
If branch doesn't exist:
git checkout -b feature/<slug>
Confirm: "Created and switched to feature/<slug>"
If branch exists:
git checkout feature/<slug>
Confirm: "Switched to existing feature/<slug>"
Output format:
feature/<slug>feature/ prefixUser request: "Start feature for user profile editing"
Process:
git branch --list feature/user-profile-editgit checkout -b feature/user-profile-editfeature/user-profile-edit. Ready to work on user profile editing."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.