ship

name	ship
description	Bring a change to shippable quality for this VS Code extension, including verification, docs/spec alignment, packaging confidence, and PR readiness.

Ship

Use this skill when the user asks to ship, ship it, prepare a PR, or take a finished change through final verification.

Goal

The current change is safe to publish or review: behavior is implemented, tests pass, docs and specs match reality, packaging works when relevant, and no known blocker is hidden.

Outcomes

• The branch contains one focused, reviewable change.
• Changed behavior is covered by tests or an explicit smoke test.
• npm run compile, npm run lint, and npm test pass.
• Web-compatible runtime, manifest, or filesystem changes also pass npm run test:web.
• Package validation passes with npm run package before PRs are marked ready.
• User-facing behavior changes update README.md and CHANGELOG.md.
• Durable behavior changes update the relevant file in specs/.
• package.json and package-lock.json remain consistent.
• Security and robustness risks from template input, JSON data, and webview output have been considered.
• The extension has been smoke tested when commands, preview lifecycle, or rendering behavior changed.
• A PR is opened and marked ready for review unless the user explicitly asks for a draft PR or a handoff-only result.
• The PR or handoff summary clearly states what changed, why, risk, smoke coverage, and verification.
• When the user asks to ship or merge, the PR is configured to merge automatically once required checks are green; if checks are already green, merge it immediately and monitor the target branch until post-merge checks complete.

Guidance

• Start by understanding the diff against the default branch and the user's requested scope.
• Fix issues as they are found instead of reporting a checklist.
• Add missing tests before declaring the change ready.
• Keep simplification scoped to changed areas unless the user asked for a broader cleanup.
• If local verification cannot run, explain the blocker and what remains unverified.
• Never claim an issue is fully closed unless every relevant task is complete.
• Do not default to draft PRs during shipping. Draft is only for explicitly requested draft work or known remaining blockers.
• For user-facing extension behavior, smoke test the real command path when practical: open a representative .handlebars document, run handlebars.preview, and verify the generated preview output.
• After opening a ready PR, check required status. If checks are pending, enable auto-merge instead of stopping for the user. If checks are green, merge immediately.
• After merge, monitor the merge commit or target branch CI. If monitoring finds a failure, keep working the root cause instead of declaring the ship complete.

Useful Commands

git status --short --branch
git diff --stat
npm run compile
npm run lint
npm test
npm run test:web
npm run package
gh pr ready
gh pr checks --watch
gh pr merge --auto
gh pr merge
gh run watch