heliohq/ship / skills/auto
auto
VerifiedRun Ship's full production workflow from raw requirement to PR: design, dev, E2E, review, QA, refactor, and handoff. Use only for explicit /ship:auto, auto pipeline requests, or end-to-end delivery.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.2 KB |
| prompts/design.md.tmpl | other | 1005 B |
| prompts/dev-fix.md.tmpl | other | 507 B |
| prompts/dev.md.tmpl | other | 657 B |
| prompts/e2e-recheck.md.tmpl | other | 755 B |
| prompts/e2e.md.tmpl | other | 1.5 KB |
| prompts/handoff.md.tmpl | other | 1.3 KB |
| prompts/qa-recheck.md.tmpl | other | 585 B |
| prompts/qa.md.tmpl | other | 1.4 KB |
| prompts/refactor.md.tmpl | other | 586 B |
| prompts/review.md.tmpl | other | 908 B |
prompts/review.md.tmpl
View on GitHubYou must use Skill('ship:review'). Skip preamble and auth gate.
Review the current diff against the spec. Write findings to the path below.
IMPORTANT: You MUST write your findings to {{TASK_DIR}}/review.md even if the
review is clean (write a short "no findings" report). The orchestrator reads
this file to decide the next phase — if it's missing, the pipeline stalls.
Do NOT only output findings to the conversation; the file is the artifact.
Report card Status rules:
- Zero P1/P2 findings → Status: PASS
- Any P1 or P2 findings → Status: FINDINGS (even if everything else is good)
P2s are real issues that the pipeline must fix. Only P3s are advisory.
spec: {{TASK_DIR}}/plan/spec.md
input_requirement: {{TASK_DIR}}/input/requirement.md
task_dir: {{TASK_DIR}}
Write review to: {{TASK_DIR}}/review.md
Mode: /ship:auto staged workflow — no user questions. Diff-only review if spec unavailable.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |