ship-cli
Manage tasks and track stacked changes
Managing work across tasks, commits, and PRs is fragmented and error-prone. This skill provides a unified workflow for Linear task management with stacked changes using Jujutsu.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"ship-cli" ์ฌ์ฉ ์ค์ ๋๋ค. I need to start working on a new feature
์์ ๊ฒฐ๊ณผ:
- Found 3 tasks ready to work on
- - TASK-456: Implement user authentication
- - TASK-789: Add dashboard widgets
- - TASK-101: Optimize database queries
- Which task would you like to start?
"ship-cli" ์ฌ์ฉ ์ค์ ๋๋ค. Show me my current stack status
์์ ๊ฒฐ๊ณผ:
- Current stack has 4 changes
- โ user/feat-auth (on track - 2/2 reviews)
- โ user/feat-dashboard (ready for review)
- โ user/feat-db (in progress - 3 commits)
- โ user/feat-api (draft - 1 commit)
"ship-cli" ์ฌ์ฉ ์ค์ ๋๋ค. Help me submit my stacked changes
์์ ๊ฒฐ๊ณผ:
- Syncing stack with trunk...
- Rebased 3 changes successfully
- Submitting stacked PRs...
- Created PR #42: feat: add authentication
- Created PR #43: feat: add dashboard widgets
- Created PR #44: feat: optimize database queries
๋ณด์ ๊ฐ์ฌ
์์ Pure prompt-based documentation skill with no executable code. Static analyzer flagged documentation text patterns incorrectly. The word 'hash' appears in JSON metadata fields (content_hash, tree_hash), backticks are markdown code formatting, and URLs are source references. All 99 findings are false positives. The skill provides workflow instructions for using external CLI tools and executes nothing itself.
์ํ ์์ธ
๐ ๋คํธ์ํฌ ์ ๊ทผ (1)
๐ ํ์ผ ์์คํ ์ก์ธ์ค (1)
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (74)
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Track personal tasks
Organize and track individual development tasks with integrated Linear and VCS workflow
Coordinate team work
Manage team progress with milestones, dependencies, and stacked PR reviews
Submit clean PRs
Create well-structured stacked changes for clean, reviewable pull requests
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
ship: action=ready
ship: action=start, taskId=TASK-123
ship: action=stack-create, message="feat: add new feature", bookmark="user/feature-slug"
ship: action=stack-sync, workdir=/path && ship: action=stack-submit, workdir=/path
๋ชจ๋ฒ ์ฌ๋ก
- Always use workdir parameter for commands in workspaces
- Run stack-sync before stack-submit to ensure clean history
- Mark tasks as done only after PR is created and merged
ํผํ๊ธฐ
- Running jj, gh pr, or git commands directly instead of using ship tool
- Skipping stack-sync before submitting work
- Moving to next task before current PR is merged
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
What tools do I need installed?
Does this work with GitHub?
Can I use this with GitLab?
Is my data safe?
Why use stacked changes?
How is this different from git branches?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
ํ์ผ ๊ตฌ์กฐ
๐ SKILL.md