# 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.

## Install

```bash
npx skillstore add edusantosbrito/ship-cli
```

## Metadata

- - Slug: edusantosbrito-ship-cli
- - Version: 1.0.0
- - Author: EduSantosBrito
- - GitHub username: EduSantosBrito
- - License: MIT
- - Repository: https://github.com/EduSantosBrito/ship-cli/tree/main/.opencode/skill/ship-cli
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: safe
- - Risk factors: network, filesystem, external\_commands
- - Quality score: 80
- - Quality tier: silver
- - Public page: https://skillstore.pages.dev/skills/edusantosbrito-ship-cli
- - Manifest: https://skillstore.pages.dev/api/skills/edusantosbrito-ship-cli/manifest

## Capabilities

- Track tasks through Linear integration with status updates
- Create and manage stacked changes with Jujutsu VCS
- Sync work with trunk and submit stacked PRs
- Handle webhook events for GitHub notifications
- Manage milestones and task dependencies

## Use Cases

- 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

## Prompt Templates

### Find ready tasks

```
ship: action=ready
```

### Start a task

```
ship: action=start, taskId=TASK-123
```

### Create stacked change

```
ship: action=stack-create, message="feat: add new feature", bookmark="user/feature-slug"
```

### Submit work

```
ship: action=stack-sync, workdir=/path && ship: action=stack-submit, workdir=/path
```

## Limitations

- Requires the ship CLI tool to be installed separately
- Works with Linear for task tracking - other tools not supported
- Jujutsu \(jj\) must be configured for version control operations

## Best Practices

- 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

## Anti Patterns

- 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

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-01-17T05:45:59.839\+00:00
- - Summary: 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.

## Stats

- - Views: 247
- - Downloads: 4
- - Favorites: 0
- - Popularity score: 0