ship
Ship
End-to-end Linear ticket → worktree → Graphite PR stack → review-agent loops → merge.
This skill is paired with the ticket skill. Normally a Linear ticket already exists; this skill picks one up. If the user wants to ship something with no ticket yet, read the ticket skill and follow its workflow to create one before continuing.
Required tools
- Linear MCP — to read tickets, list issues, change status, and post comments.
gt(Graphite) — PR stackgh(GitHub CLI) — PRs and review-agent comments
If any is missing, stop and ask.
Approval gates
The agent never advances past these without explicit user confirmation ("yes", "approved", "merge", etc.). Permission does not carry over between gates.
| # | Gate | When |
More from ilamanov/skills
spec-builder
Transform vague product or feature ideas into concrete, detailed specification documents through an interactive interview process. Use when the user wants to flesh out an idea, create a spec, write requirements, plan a product/feature/prototype, or go from "I have this idea..." to a concrete document. Works for software products, physical products, services, or any concept that needs specification.
23pr
Commit changes and create or update a pull request following project standards. Use when the user wants to commit work, create a PR, update an existing PR, or use the /pr command.
14reimplement-branch
Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when the user wants to clean up messy commits, create a tutorial-style commit history, or prepare a branch for review with logical, self-contained commits. Triggers on requests like "clean up my commits", "reimplement this branch", "create a clean history", or "make my commits reviewable".
12deslop
Remove AI-generated code slop and clean up code style
10compile-conversation-into-doc
Turn long, messy AI chat conversations into clear, durable, and easily scannable reference documents that humans can reliably return to weeks or months later.
9review-bug-fixer
Fix valid code review findings from one or more review markdown files. Use when the user has review files (e.g., review1.md, review2.md) containing code review findings, issues, or suggestions and wants to fix the valid ones in the current branch. Triggers on requests like "fix review findings", "fix issues from review", "apply code review fixes", or any mention of fixing bugs/issues from review markdown files.
8