Turn your repository's real preflight routine into a `/ship` skill. It checks the commit, runs the correct lint and build commands, pushes the branch, watches CI, fixes minor failures, and reports when the pull request is ready.
Download the skill for this workflow. Version 1.0.1.
with Claire Vo
Alex opens his personal dev box skills and shows `/ship` running repository checks, pushing the branch, monitoring Buildkite, and retrying minor CI fixes before he returns.
A reusable `/ship` skill that takes a ready branch through local checks, push, CI monitoring, minor fixes, and a final status report.
AI pair programmer
Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.
6 steps
Copy the repository's actual premerge routine into one checklist. Include commit inspection, lint, targeted tests, build commands, branch push, pull request lookup, CI status, and the minor failures that are safe for the agent to repair.
Create a /ship skill from that checklist. Use exact commands, define which CI failures may be repaired, cap retries, and require a final status report. Keep destructive actions and secrets out of the automation.
Create a `/ship` skill for this repository. First inspect the current commit for unrelated files or credentials. Run `[repository lint command]`, `[repository test command]`, and `[repository build command]`. If they pass, push the current branch without force and find or open its pull request. Monitor `[CI provider]` for up to one hour. For a minor lint or formatting failure, apply the smallest fix, commit it, push, and retry, up to five total attempts. Stop on repeated failures or changes outside the failing check. Finish with the pull request URL, commits pushed, checks run, and current CI status.
Implement the local preflight phase with the same commands developers already use. Inspect the commit, run lint, tests, and the correct build target, then push the current branch only after those commands pass.
Add pull request and CI polling. When a minor lint or formatting job fails, read the log, make the smallest relevant change, commit it, push, and continue monitoring. Stop at the retry or time limit and report the remaining failure.
Keep a few hard constraints inside the skill: never force push, never add credentials, never rewrite shared branch history, and never hide a failed check. These are stable operating rules, not a separate approval ceremony.
Safety constraints are crucial for giving the team confidence to use powerful automation tools.
When the branch is ready, run /ship and move on to other work. Return to the final report or notification, which should identify the pull request, the checks that ran, any repair commits, and whether CI is green.
Turn an idea into a PRD, user stories, and a plan.
How to recover when the loop fails and where human judgment helps.
Create a repository-based system to provide an AI assistant with durable context about your team, projects, and communication channels. This enables it to perform routine tasks like summarizing daily updates and identifying stakeholders, acting as a personalized chief of staff.
Use Meta's Muse to generate a printable, multi-page family newspaper that includes a weekly schedule, weather forecasts, and activity ideas. This workflow leverages Muse's strength in creating visually appealing, family-oriented artifacts.
Coordinate agents in Slack and Cursor to propose growth experiments for human review. Ezra’s Auto XP system was still being developed at the time of the episode.
Join 250,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.
