# Ship Check

> Verify work before committing, pushing, or requesting review

- Skill: `lucassantana-dev/ship-check` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add lucassantana-dev/ship-check`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lucassantana-dev/ship-check/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: LucasSantana-Dev (https://skillmd.com/u/lucassantana-dev)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/lucassantana-dev/ship-check

---


# Ship Check

Run the repo's own verification commands and report pass/fail with evidence — before any git operation.

## Steps

1. **Inspect changes** — review staged and unstaged files, diff summary
2. **Discover verification commands** — look for lint, typecheck, test, build scripts
3. **Run each command** — capture exact output and exit codes
4. **Report results** — pass/fail per command with evidence

## Output

```text
Files changed: <count>
Lint:          PASS | FAIL
Typecheck:     PASS | FAIL | N/A
Tests:         PASS | FAIL | N/A
Build:         PASS | FAIL | N/A
Blockers:      <list or none>
```

## Rules

- Never invent tests or build commands that don't exist in the repo
- Never mark work ready when verification was skipped
- Refuse to claim success without command output evidence
- Report blockers explicitly instead of hiding failures