ship

Commits verified work, merges to main, pushes, and confirms the deployed site renders.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/robritacca-dotcom/design-system --skill ship-robritacca-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/robritacca-dotcom/design-system/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/robritacca-dotcom/design-system --skill ship-robritacca-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a personal site by hand invites mistakes: unrelated files swept into commits, unverified builds pushed to main, and deploys that return HTTP 200 while serving a blank page. This Skill enforces a disciplined release pipeline so every push to robertritacca.com is verified, scoped, and proven live. ## Core Features & Use Cases - Scoped commits: Surveys the working tree, classifies files as in-scope or out-of-scope, and never uses blanket git add -A, keeping unrelated changes out of the release. - Full local verification: Runs the single npm run verify script mirroring CI before anything is committed, plus a delta-scoped prose check against README and spec docs. - Branch merge and push: Merges feature branches into main, pushes (which triggers the Vercel deploy), watches the GitHub Actions CI run to green, and cleans up merged branches. - Live deploy proof: Confirms the new deployment ID is serving, then runs a hydration smoke test against the live site at desktop and mobile viewports, treating failure as an active outage. - Use Case: After finishing a new portfolio case study on a feature branch, ask to ship it — the Skill verifies the build, merges, pushes, watches CI, and proves the live site renders before reporting what deployed. ## Quick Start Ask the assistant to ship the finished work and make it live on robertritacca.com.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Next.js site to Vercel by pushing to main?

Commit your verified changes, merge into main, and run git push — the push triggers the Vercel deployment automatically. This Skill then watches the GitHub Actions CI run and confirms the new deployment ID is serving before declaring the release done.

How do I avoid committing unrelated files in Git?

Run git status --short and classify every entry as in-scope or out-of-scope before staging. Always add explicit file paths instead of git add -A or git add ., and name any excluded files in the final report.

Why does a deploy return HTTP 200 but show a blank page?

A green build and HTTP 200 do not prove the page renders — runtime rendering failures like ISR regeneration errors only appear in a real browser. This Skill runs a hydration smoke test against the live site at desktop and phone viewports to catch exactly this failure.

What happens if the post-deploy smoke test fails?

A red smoke test is treated as an active outage, not a report line. The Skill diagnoses immediately, and if the cause is not quickly fixable, it reverts the deploy with git revert and pushes again rather than leaving the site dark.

Can I use this to save progress without deploying?

No — this Skill always ends with a deploy to production. To save progress without deploying, use a checkpoint-style workflow that pushes the branch while keeping work off main.