Skills

Ship

Ship the current branch to main.

Install

npx skills add nightly-labs/openbot --skill ship -g -a claude-code -y
Repository
nightly-labs/openbot4.5k
Category
Git and review
Updated
3d ago
License
See repository
Context cost
Mediumabout 1,766 tokens
Runs scripts
No, instructions only

What it does

Ship the current branch to main. Review the diff, fix findings, open the pull request, babysit the NorbiAI review and CI until green, then squash-merge. Use when a feature is done and the user asks to ship it, open and merge a PR, or get the change to main.

Ship

Move one finished branch to main through five gates: local review, pull request, NorbiAI review, CI, merge. Do each gate in sequence. Do not skip a gate to go faster.

When the user invokes this skill, they approve the merge at the end, but only when every gate is green. Stop and ask when a gate needs a product decision, a force-push, or a bypass.

Before you start

  • Read AGENTS.md and each nested AGENTS.md for a directory in the diff.
  • Run git status and git branch --show-current. When the branch is main, create a branch first. Do not ship from main.
  • Run git fetch origin main. Get the change set with git diff --stat origin/main...HEAD and git status --short.
  • When a pull request for the branch exists (gh pr view --json number,state,url), continue from the first gate that is not done.
  • Keep a checklist in TASKS.md with one item for each gate.

Gate 1, Review the diff locally

A local review is less expensive than a NorbiAI round. Find the problems before the push.

  1. Commit the finished work. Write the message in ASD-STE100 Simplified Technical English. Leave unrelated changes out of the commit.
  2. Review origin/main...HEAD for correctness, data loss, the non-negotiable rules in AGENTS.md, and reuse. Use the code-review skill when it is available, or a review subagent with the diff range.
  3. Triage each finding as babysit Step 2 says: fix only findings that you can prove. Record the others as not valid, with the reason.
  4. Run the narrowest relevant test file and biome check --write --max-diagnostics=none <changed paths>. Run one typecheck project for the code you changed, as AGENTS.md says. Do not run broad checks.
  5. Commit the fixes. The pre-commit hook runs its own checks. Do not use --no-verify. When the hook fails, fix the cause and commit again.
Read the whole SKILL.md on GitHub

More in Git and review