dev-ship
/dev-ship
Use to ship a finished branch. Triggers include "ship", "push", "open PR", "ship it". Runs ALL test suites, pushes, opens or updates the pull request, and watches CI until it passes or fails. Never merges.
- Author
- tejitpabari99 ↗
- Repository
- tejit-plugin ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use to ship a finished branch. Triggers include "ship", "push", "open PR", "ship it". Runs ALL test suites, pushes, opens or updates the pull request, and watches CI until it passes or fails. Never merges.
Triggers from the description
Original author description
Use to ship a finished branch. Triggers include "ship", "push", "open PR", "ship it". Runs ALL test suites, pushes, opens or updates the pull request, and watches CI until it passes or fails. Never merges.
How it works
- Steps
SKILL.md preview
---
name: dev-ship
description: Use to ship a finished branch. Triggers include "ship", "push", "open PR", "ship it". Runs ALL test suites, pushes, opens or updates the pull request, and watches CI until it passes or fails. Never merges.
metadata:
version: "0.1.0"
---
# dev-ship — Test, Push, PR, CI
Before anything else, follow `../_shared/update-check.md`.
Section names below (Workspace guard, Test policy, CI default, Question rules, Auto mode,
Review cadence, Handoff) are in `../_shared/dev-common.md`. Never merge. Never force push.
## Steps
1. **Ship gate.** `gh pr view --json number,url,state` for the current branch. Only
`state` OPEN counts as an open PR; merged or closed counts as no PR.
- Open PR exists: ship directly, no question.
- No open PR: if the user directly asked to ship (said "ship", "push", "open PR"), that
is the yes. Otherwise ask exactly one yes/no, "Ship?" (default yes). Auto mode never asks. No other
question about push, PR, title or base branch. A "no" ends the skill; keep the Handoff.
2. **Workspace guard.** Apply it. Then `git pull --ff-only` if the branch has an upstream.
3. **Run ALL test suites** in the repo. Find the commands in the project rules, the CI
workflow, and package files (`package.json`, `pyproject.toml`, `Makefile`, and so on).
This is the only skill that runs the whole suite (Test policy). On failure, fix through
`dev-code` fix-only, then rerun. Max 3 rounds, then stop and report.
If no CI workflow runs the tests, warn once at the end; do not add one (CI default).
4. **Push.** `git push -u origin <branch>`.
- No PR: `gh pr create --base <default-branch> --title <title> --body-file <file>`, body
filled from `pr-template.md`.
- PR exists: regenerate the body from `pr-template.md`, `gh pr edit <n> --body-file <file>`,
then push.
- If `gh pr edit --body-file` fails (for example a Projects classic GraphQL error), fall
back to `gh api -X PATCH repos/<owner>/<repo>/pulls/<n> -F body=@<file>`.
- At push time, write `pending` in the body's CI section.
5. **Watch CI.** Dispatch a CI monitor sub-agent. It runs this as a background command, so
no model turn is spent per check, then ends its turn and reports when the command exits:
```
timeout 1800 gh pr checks <n> --watch --interval 300
```
It re-checks every 5 minutes for at most 30 minutes. By exit status:
- `0`: all checks passed. The agent closes; report the PR URL.
- `124` (timeout): still pending after 30 minutes. Report pending and stop.
- other non-zero: a check failed (or none exist; see below). Get the run ID from
`gh pr checks <n> --json link`, then the logs with `gh run view <run-id> --log-failed`.
Fix through `dev-code` fix-only, go back to step 3. Max 3 CI rounds, then stop and
report.
- No checks reported: right after a push they may not have started. If a workflow file
exists, retry every 60 seconds for 5 minutes before concluding none are configured.
If still none, warn, finish.
After the CI result (pass, fail or timeout), update the PR body's CI section with the
result, using the same edit and fallback as step 4.
6. **Handoff.** On success remove this section of `_next-context_.md` (Handoff). On a stop,
write what failed and what is next, then end with the "Continue here" message (skipped in
auto mode).
Files in this package (2)
- SKILL.md 3 KB
- pr-template.md 1 KB
Versions
The database has no other skills named dev-ship.
Database snapshot: 13.11.2026 · package version 51c6e1132c65 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86ship
Ship phase. Commit the change, push the branch, and open the PR with test results and evidence attached. Use when the user says "ship", "open the PR", or after a green verify inside /el-combo:build. - 90ds-ready
Runs the full ds-ship workflow but stops with the pull request ready for a human to merge, and never merges. Use when the user says get it ready, make it mergeable, stop before merge, or /ds-ready. - 90open-pr
Bring the branch up to date, push it, open the pull request for an issue in the body shape of the repository, and watch CI. The implement-issue skill uses it. Use it directly when a branch is ready. - 100rc-git
Moves work onto a branch, pushes, opens a PR; also rebase and conflicts. Use to ship local work. Do not use to commit in place. - 90st-ready
Runs the full st-ship workflow but stops with the pull request ready for a human to merge, and never merges. Use when the user says get it ready, make it mergeable, stop before merge, or /st-ready. - 86ship
Take a change from a branch to merged and cleaned up - open or update a pull request and see it through review, self-review the branch, merge, clean up after. Use when asked to open or update a PR, review your own branch, merge, or clean up after a task.