Ticket Ship

Community

OutThisLife

ticket-ship

Take a tracker ticket through to shipped: find or start the PR, drive it to mergeable, update the ticket state, draft the stakeholder message. Use for Jira/Linear (or acli) tickets assigned to you.

Overview

Publisher	OutThisLife
Repository	`brooklyn-skills`
Skill name	`ticket-ship`
Stars	200
Forks	6
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by OutThisLife on GitHub. Read the source before you install it.

Installation

Install the Ticket Ship AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/OutThisLife/brooklyn-skills/tree/main/skills/ticket-ship
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/OutThisLife/brooklyn-skills.git /tmp/brooklyn-skills
mkdir -p .claude/skills
cp -r /tmp/brooklyn-skills/skills/ticket-ship .claude/skills/ticket-ship

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ticket Ship in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ticket Ship on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ticket Ship is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Ticket → Ship

The ticket-shaped parts of shipping. The PR mechanics live in their own skills — this is what a tracker adds on top.

Steps

Read the ticket and its latest comments, then list existing PRs before starting (acli, Jira, Linear, gh). With acli, request --fields summary,description,status,comment,issuelinks --json: the default view omits comments, which can contain reopened QA scope. Read the existing PR diff as well as its body; follow-up commits can invalidate the body's implementation claims.
Confirm the correct base branch(es) before starting — some orgs need a release branch plus the default (stacked-pr). Never assume; verify the org's rule.
Find the existing PR or start one (work → pr-update), then drive it mergeable (pr-ready) and polish before handoff (clean).
Read the repository's ticket/label guidance before selecting a handoff state; don't substitute generic workflow names. In MR, use .claude/skills/create-pr/SKILL.md and teams.md for label rules. For an existing DOTCOMPB PR returned by QA and then fixed, the user's retest handoff is In Test with Pending QA Review, not a reset to In Code Review. Preserve the ticket-driven Needs UI Review label. Report CI/deployment blockers separately; In Test does not mean merge-ready. Link the PR and add a factual retest update when the user requests the handoff.
Draft the stakeholder update — Slack or a ticket comment, short, no-tropes. Don't send it unless asked.

Don't

Assume the base branch.
Mark the ticket done while CI is red or review threads are open.
Let the ticket and the PR tell different stories about the state of the work.

Frequently asked questions

What does the Ticket Ship AI skill do?

Take a tracker ticket through to shipped: find or start the PR, drive it to mergeable, update the ticket state, draft the stakeholder message. Use for Jira/Linear (or acli) tickets assigned to you.

Why use Ticket Ship on TypingMind?

Because you install it once and use it with any model. Ticket Ship is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ticket Ship in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/OutThisLife/brooklyn-skills/tree/main/skills/ticket-ship. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ticket Ship?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ticket Ship?

As many as you like. As long as a model supports skills, you can use Ticket Ship with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ticket Ship AI skill free?

Yes. It is published on GitHub by OutThisLife under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Auto Qa

openclaw

OrganizationPopular

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Clawsweeper

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Ticket → Ship

Steps

Don't

Frequently asked questions

Related AI Skills

Set up your own AI workspace now