Ship Check
Overview
Run the repo's end-of-task validation flow after code or documentation changes.
This is an orchestration skill. It does not replace the specialized review skills. It tells the agent which checks to run, in what order, and how to summarize the result before final handoff.
Standard Flow
Use this flow after finishing a fix, refactor, or feature:
- Review the latest changes with .
- Check whether project documentation needs maintenance with .
- Report the combined outcome clearly.
- If code changed, remind the user about any validation commands not yet run.
Invocation Pattern
When this skill is invoked, explicitly use the other repo-local skills in sequence.
Start with:
Use $review-changes to review the latest changes against the project's guidelines and report findings first.
Then run:
Use $repo-doc-maintainer to review the latest changes and decide whether project documentation should be updated.
Do not skip either step unless the user explicitly narrows the scope.
How To Interpret Results
If finds issues
- present the findings first
- do not claim the work is validated
- if the issues are actionable and local, fix them before final handoff when appropriate
- rerun validation after fixes if you changed the code again
If finds no issues
- say that the changes comply with the current repo guidance
- still run
If says docs should change
- update the docs if the current task includes making those maintenance edits
- otherwise report that documentation maintenance is recommended
If says no doc update is needed
- state that explicitly in the final close-out
Output Expectations
The final close-out should combine both checks:
- whether the implementation passed the repo-rule review
- whether documentation maintenance was needed
- whether project validation commands were run or remain outstanding
Keep the output compact. Prefer a brief status summary over a long checklist unless there are actual findings.
Constraints
- Treat as the source of truth for repo-rule compliance review.
- Treat as the source of truth for doc-maintenance decisions.
- Do not invent a separate third review rubric here.
- Use this skill at the end of work, not before implementation starts.
Validation Flow
Use this checklist after finishing implementation work.
Required Review Skills
Default Sequence
- Inspect the latest working tree or commit range.
- Run the repo-rule review via .
- Run the doc-maintenance review via .
- Summarize both results.
Final Close-Out Should Cover
- whether the changes respect the project's documented guidelines
- whether project documentation needed updates
- whether validation commands (lint, test, analyze) were run
- any residual risks, such as unrun tests or manual-only verification gaps
When To Re-Run
Re-run the flow if you make additional code or doc edits after the first validation pass.
Closing Signal
After the final close-out, always emit a verdict on its own line:
- — if both checks passed with no outstanding issues
- — if issues were found or remain unresolved, followed by a structured findings block:
**Findings:**
- review-changes: <summary of issues, or "passed">
- repo-doc-maintainer: <summary of doc recommendations, or "no changes needed">
- validation commands: <any outstanding commands not yet run, or "all run">
The
line must be the last substantive output.