メニュー
Ship a Linear issue end-to-end: read issue, create Linear branch, implement, commit, push, open PR, and move issue to In Review. Trigger when the user provides a Linear issue ID (for example `ML-123`) and asks to implement/ship.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Cuts a new release of ai-sdk — creates a Linear issue, branches, bumps version, updates changelog, runs checks, commits, opens a PR, and returns to main. Merging the PR triggers CI to auto-tag. Use when the user wants to release a new version of the ai_sdk gem.
References Semaphore's sem-ai CLI command set, output formats, safety defaults, and legacy sem replacement patterns. Use when exact sem-ai commands or flags are needed before inspecting or mutating Semaphore state.
Debugs and triages Semaphore CI pipelines and jobs with sem-ai first, falling back to legacy sem only for interactive attach/debug shells. Use when CI is failing, flaky, stuck, queued, or needs logs, reruns, stops, or deployment-state inspection.
Find an unreserved staging namespace and promote a Semaphore pipeline into it. Use when a user asks to pick a free `revNN`/`qaNN` server, trigger `Deploy to EKS staging`, or validate that promotion/deploy completed.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
Promote an Amadeus PR to the shared `data` staging namespace using Semaphore `Deploy to Staging`, then verify the SLSA-backed artifact flow, deployed image, and live log contract through Kubernetes.
| name | ship |
| description | Ship a Linear issue end-to-end: read issue, create Linear branch, implement, commit, push, open PR, and move issue to In Review. Trigger when the user provides a Linear issue ID (for example `ML-123`) and asks to implement/ship. |
Execute a Linear issue from input to PR with one default flow.
ML-123.[<ISSUE-ID>] <Issue Title>.Fetch issue details from Linear:
git checkout main
git pull origin main
git checkout -b <resolved-branch-name>
Use the issue description as scope.
[<ISSUE-ID>] <Issue Title>.git push -u origin <branch-name>
If a PR template exists, apply it first and append the generated summary after template content.
Choose a PR label. First, consult the repo's existing labels (gh label list) for a match based on issue type or content. If no suitable label is found, ignore label assignment.
git checkout main
Move the Linear issue to In Review after PR creation.
main at the end.In Review.