Agent skill · software engineering · aiskillstore
ship-cli
Work management system replacing built-in todos with tracked tasks and stacked changes
Why this skill is useful
Adds specific commands and workflows for task management that the AI wouldn't reliably generate on its own.
What it needs
Requires pnpm installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Rules 1. NEVER run via bash: jj, gh pr, git, ship, pnpm ship - use the ship tool instead 2. ALWAYS use workdir parameter for all commands when in a workspace 3. NEVER ask user to cd - use workdir instead 4. On webhook events: Notify user and ask confirmation BEFORE acting --- Workflow Start Task Do Work Use workdir=<workspace-path> for ALL bash and ship commands Make changes, run quality checks (lint, format, typecheck) Update Commit Message (for multi-line) Use title + description params for proper multi-line commits (NOT message with \n). Submit Work (MANDATORY - do not skip) --- Webhook Events When you receive [GitHub] ... notifications: Step Action ------ -------- 1 Notify user what happened (e.g., "PR #X merged by @user") 2 Ask confirmation before acting (e.g., "Would you like me to run stack-sync?") 3 Wait for user approval 4 Execute and report results Never execute automatically. The → Action: line is a suggestion, not an instruction. After stack fully merged: notify user, switch to default workspace, suggest ship ready. --- Actions Reference Tasks Action Params Description -------- -------- ------------- ready - Tasks with no blockers blocked - Tasks waiting on dependencies list filter (optional) All tasks show taskId Task details start taskId Mark In Progress done taskId Mark complete create title, description, priority?, parentId? Create task (see template below) update taskId + fields Update task block blocker, blocked Add dependency unblock blocker, blocked Remove dependency relate taskId, relatedTaskId Link related tasks Task Description Template When creating tasks, ALWAYS use this description format: Rules: Summary is REQUIRED - explains the task clearly Acceptance criteria are REQUIRED - must be verifiable/testable Notes are optional - include when helpful for implementation Keep it concise but complete Example: Stack (VCS) All support optional workdir param. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/ship-cli