Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From ship
Analyzes staged and unstaged Git changes, proposes branch names following a naming convention, and creates the selected branch.
How this command is triggered — by the user, by Claude, or both
Slash command
/ship:SKILL [context or ticket number]haikucheckout/This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /checkout - Git Branch Creation Analyze Git changes, propose branch names that follow the naming convention, and create a new branch with the name the user picks. ## Input `$ARGUMENTS` may contain context or a ticket number. Trim whitespace; if empty, analyze the Git changes alone. If non-empty, treat it as a hint for the branch name scope or ticket ID. ## Execution 1. Run `git status` and `git diff` in parallel to read the changes 2. Generate 3 branch name candidates that follow the naming convention from the changes and `$ARGUMENTS` 3. Present each candidate with a selection reason...
Analyze Git changes, propose branch names that follow the naming convention, and create a new branch with the name the user picks.
$ARGUMENTS may contain context or a ticket number. Trim whitespace; if empty, analyze the Git changes alone. If non-empty, treat it as a hint for the branch name scope or ticket ID.
git status and git diff in parallel to read the changes$ARGUMENTSAskUserQuestion and let the user pick onegit checkout -b <selected name>Determine the type from the changes (each type's trigger is in the table below) and assemble the branch name in this format.
<type>/<scope>-<description>
<type>/<ticket>-<description>
| Prefix | Use Case | Trigger |
|---|---|---|
| feature/ | New functionality | New files, components |
| fix/ | Bug fixes | Error corrections |
| refactor/ | Code improvements | Restructuring |
| docs/ | Documentation | .md files, README |
| test/ | Test additions/fixes | Test files |
| chore/ | Maintenance | Dependencies, config |
| perf/ | Performance | Optimization, caching |
$ARGUMENTS has a ticket ID, include it at the <ticket> position; do not include dates| Error | Action |
|---|---|
| No changes | Report there are no changes |
| Branch exists | Suggest an alternative name |
| No git repository | Report it is not a git repo |
Report the created branch name on a single line.
npx claudepluginhub thkt/dotclaude --plugin ship/newbranchCreates a new git branch from the latest origin/main, stashing and restoring uncommitted changes. Auto-generates branch names from context or accepts user-provided names. Also supports cherry-picking commits from the previous branch.
/create-branchCreates a new feature branch with optimized short naming and auto-incrementing numbers, from a description or auto-generated from uncommitted changes.
/commitAnalyzes unstaged changes, stages relevant files excluding secrets, generates a conventional commit message matching repo style, and commits. Protects main branch by prompting for feature branch.
/update-branch-nameAnalyzes git changes against main branch and updates current branch to a descriptive name based on the work done.
/commit-push-prCommits current changes (staged/unstaged) to a new branch if on main, pushes to origin, and creates a GitHub pull request via gh.
/SKILLCreates a GitHub pull request with automated quality validation, security scanning, issue linking, and compliance checks. Accepts optional description or issue reference.