| name | ship-change |
| description | Close out finished vapid.party work with verification, git hygiene, commit, push, and a clean final status. Use when a discrete code, docs, memory, or skill change is complete; when the user asks to land work; or before reporting that repo work is done. |
Ship Change
Overview
Finish work in the repo's expected shape: verified, committed, pushed, and reported with any blocked checks called out.
Workflow
- Check current state:
git status --short --branch
- Review the diff:
git diff --check
git diff --stat
git diff
- Run checks relevant to the touched files:
npm run lint
npm run build
Run npm test when tests exist, changed behavior warrants it, or the user asked for it.
- If skills changed, validate each changed skill:
python3 /home/pierce/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/<name>
- Stage only intended files.
- Commit with a concise message.
- Push to
origin main unless the repo is on a different active branch or the user requested another flow.
- Re-run
git status --short --branch and report the clean or blocked state.
Guardrails
- Do not stage unrelated user changes.
- Do not hide failed checks; report the exact command and failure class.
- Do not commit secrets or local environment files.
- If push needs network approval, request it and continue once approved.
