Skip to content
Skills Library
Programming · Automation

principle-ship

/principle-ship

Apply when finishing a code change, or when asked to ship, merge, deploy or call a task done. Done means a PR opened, the diff self-reviewed, CI green, merged, and the deploy confirmed live.

Repository
RayStack ↗
Licence
MIT
Last repository change
06.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Apply when finishing a code change, or when asked to ship, merge, deploy or call a task done. Done means a PR opened, the diff self-reviewed, CI green, merged, and the deploy confirmed live.

Original author description

Apply when finishing a code change, or when asked to ship, merge, deploy or call a task done. Done means a PR opened, the diff self-reviewed, CI green, merged, and the deploy confirmed live.

How it works

  1. Settings
  2. Steps
  3. Never
  4. Stop and report
Original SKILL.md headings · 36 lines, 317 words
SKILL.md preview
---
name: principle-ship
description: Apply when finishing a code change, or when asked to ship, merge, deploy or call a task done. Done means a PR opened, the diff self-reviewed, CI green, merged, and the deploy confirmed live.
---

# Ship

A change is done when it runs in production, not when the PR is open.

## Settings

Read `.raystack.json` at the repo root, else `~/.raystack.json`. No file or no key: use the defaults.

```json
{ "ship": { "autoMerge": false, "deployCheck": "Deploy workflow on main, then GET /health" } }
```

- `autoMerge` (default `false`): stop at green CI and ask through the question tool before merging. `true`: merge on green without asking.
- `deployCheck`: how to confirm the deploy (a workflow name, a URL, a health check). Unset: find it in the repo (CI workflows, README) and say which check you used.

## Steps

1. Work on a feature branch. For a user-facing change, run `local-verify` first. Open a PR.
2. Read the whole diff yourself before anyone else does, and check the docs still match the code. Fix what you find.
3. Wait for CI. Every required check must pass.
4. Merge, or ask first, per `autoMerge`.
5. Wait for the deploy to finish. Confirm it is live with a fresh request, a health check, or the deployed revision matching the merge commit.
6. Report what you confirmed and how. No git remote: skip the PR, CI and deploy. Merge into the default branch locally (ask first per `autoMerge`), run the tests there, and report "merged locally, not deployed".

## Never

- Merge with failing or pending required checks.
- Force-push a shared branch, push straight to the default branch, or skip hooks.
- Close the task on partial evidence. "Merged", "deployed" and "verified live" are three different claims. A green deploy job is not a page that loads.

## Stop and report

- CI or the deploy fails: say what failed and quote the log line.
- The change publishes, charges money, submits to a third party or drops data, and nobody approved that step. A blanket "go ahead" does not cover it.

Versions

The database has no other skills named principle-ship.

Database snapshot: 13.11.2026 · package version 9a4aaab4e70b (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

  • 85swe-310-merge-after-review
    Merge a pull request only when it's approved, green on the latest commit, unchanged since approval, and revertible. Use when asked to merge, land or ship a reviewed change into the main branch.
  • 100ship
    Ship the current branch to {%defaultBranch%}. Review the diff locally, open the pull request, babysit the AI review when the change is high risk and CI until green, then squash-merge. Use when a change is finished and the developer asks to ship it, merge it, or get it to {%defaultBranch%}.
  • 90st-ship
    Takes a change all the way from code to a merged pull request without supervision: build it, prove it, review it, file the PR, watch it and merge it. Use when the user says ship it, send it all the way, merge when green, or /st-ship.
  • 100relay-ship
    End-to-end ship workflow — merge base, run tests, review diff, bump version, commit, push, create PR. Use when asked to "ship", "push to main", "create a PR", "get this merged", or "deploy this branch".
  • 100ship
    Orchestrates the current branch from "code done" to "merged": runs the review-code skill, then any project-specific pre-merge checks it detects (visual regression like `just visual-diff`, tests, lint), then a conventional commit per git-commit, a PR per git-create-pr, and…
  • 90ds-ship
    Takes a change all the way from code to a merged pull request without supervision: build it, prove it, review it, file the PR, watch it and merge it. Use when the user says ship it, send it all the way, merge when green, or /ds-ship.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.