neonwatty/linkparty · Archived

ship

Check CI, merge PR, pull main, and verify deployment. Use when ready to ship the current branch.

First seen Apr 7, 2026

Installation

$ npx skills add neonwatty/linkparty --skill ship

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from neonwatty/linkparty.

npx skills add neonwatty/linkparty

Browse all from neonwatty/linkparty

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,325 B
  • docs SUMMARY.md 108 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Ship the current branch by checking CI, merging, and verifying deployment.

Steps

  1. Check CI status — Run gh pr checks on the current branch
  2. Wait if pending — If any checks are still running, poll every 30 seconds (max 5 minutes). Show a brief status update each cycle.
  3. Handle failure — If any check fails:

- Run gh run view <run-id> --log-failed to get the failure logs - Summarize what failed and why - Stop and report — do NOT merge

  1. Merge — If all checks pass:

- Run gh pr merge --squash --delete-branch - If merge fails, report the error

  1. Update local — Switch to main and pull:

- git checkout main && git pull

  1. Verify deployment — Check Vercel deployment status:

- gh api repos/{owner}/{repo}/deployments --jq '.[0] | {state, environment, created_at}' - Report deployment state

  1. Summarize — Output what was shipped: PR title, number of commits, deployment status

Important

  • Never force-merge or skip CI checks
  • If CI has been running for more than 10 minutes total, stop waiting and report
  • If there's no open PR for the current branch, say so and stop