Starlight Ship
Purpose
Turn “the code seems done” into a reproducible release decision while preserving unrelated work and repository governance.
When it fires
- A change is ready to commit, push, open for review, merge, or deploy.
- The user asks for release, landing, PR, or Git/Vercel operations.
- A stale or failing PR needs evidence-based disposition.
Inputs
- Repository instructions, branch policy, and required checks.
- Exact diff, test results, review findings, deployment state, and rollback path.
- User authority for commit, push, merge, production, publication, and cleanup.
Workflow
- Verify path, repository root, origin, branch, and working-tree ownership.
- Inspect the complete diff and exclude unrelated user changes.
- Run proportionate tests, lint/type gates, secret scan, and diff checks.
- Use a preview deployment for web changes when the repository supports it.
- Record independent review findings and resolve blockers.
- Confirm mergeability, required checks, release notes, rollback, and post-merge monitoring.
- Execute only the authorized Git or deployment action; never force-push or rewrite shared history by default.
Output contract
Return revision, diff scope, gates and results, review status, preview/production state, known limitations, rollback, action taken, and remaining human decisions.
Tools & MCP
Use non-interactive Git, the repository’s CI, secret scanner, and hosting connector. Preserve dirty worktrees, avoid destructive reset/checkout commands, and stop session-owned servers.
Quality bar
- “Green” means required gates passed on the exact head revision.
- Skipped or unavailable checks are explicit.
- A successful preview is not called a production release.
- Merge or deployment follows branch protection and human authority.
Example
Input: “Land PR 21 if it is ready.”
Good output: verify the exact head, required CI and security reviews, run release smoke tests against the preview, resolve comments, merge using repository policy, verify production, and retain a rollback revision.
Built on SIP — Starlight Intelligence Protocol
Vertical: starlight-agent-skills · portable capability layer
1---2name: starlight-ship3description: Prepare an authorized change for review or landing by checking repository state, required gates, secrets, diff scope, deployment evidence, rollback, and merge policy. Use when a branch or pull request is ready for a release decision; never rewrite, merge, deploy, or publish without the authority granted for that action.4---56# Starlight Ship78## Purpose910Turn “the code seems done” into a reproducible release decision while preserving unrelated work and repository governance.1112## When it fires1314- A change is ready to commit, push, open for review, merge, or deploy.15- The user asks for release, landing, PR, or Git/Vercel operations.16- A stale or failing PR needs evidence-based disposition.1718## Inputs1920- Repository instructions, branch policy, and required checks.21- Exact diff, test results, review findings, deployment state, and rollback path.22- User authority for commit, push, merge, production, publication, and cleanup.2324## Workflow25261. Verify path, repository root, origin, branch, and working-tree ownership.272. Inspect the complete diff and exclude unrelated user changes.283. Run proportionate tests, lint/type gates, secret scan, and diff checks.294. Use a preview deployment for web changes when the repository supports it.305. Record independent review findings and resolve blockers.316. Confirm mergeability, required checks, release notes, rollback, and post-merge monitoring.327. Execute only the authorized Git or deployment action; never force-push or rewrite shared history by default.3334## Output contract3536Return revision, diff scope, gates and results, review status, preview/production state, known limitations, rollback, action taken, and remaining human decisions.3738## Tools & MCP3940Use non-interactive Git, the repository’s CI, secret scanner, and hosting connector. Preserve dirty worktrees, avoid destructive reset/checkout commands, and stop session-owned servers.4142## Quality bar4344- “Green” means required gates passed on the exact head revision.45- Skipped or unavailable checks are explicit.46- A successful preview is not called a production release.47- Merge or deployment follows branch protection and human authority.4849## Example5051Input: “Land PR 21 if it is ready.”5253Good output: verify the exact head, required CI and security reviews, run release smoke tests against the preview, resolve comments, merge using repository policy, verify production, and retain a rollback revision.5455---5657Built on SIP — Starlight Intelligence Protocol58Vertical: starlight-agent-skills · portable capability layer
frankxai