skills.rest
jukqaz
jukqazCOMMUNITY
Explore all skills by this author →
GitHub

ship-check

Identify code, configuration, documentation, and test changes and verify them with targeted checks.

Updated Aug 23, 2026
Search Tags:#workflow#testing#debugging#verification#code-change#smoke-test#ship-check
One-click install
npx skills add https://github.com/jukqaz/stack-pilot --skill ship-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-check
Source: https://github.com/jukqaz/stack-pilot/tree/main/addons/stackpilot-dev-kit/codex/skills/ship-check
Command: npx skills add https://github.com/jukqaz/stack-pilot --skill ship-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ship-check skill helps teams verify changes by running only the smallest credible verification set, reducing noise while preserving confidence in completion.

Core Features & Use Cases

  • Targeted verification: syntax/parse checks first, followed by typecheck/lint, focused tests, and runtime smoke tests.
  • Clear justification: if a stronger check is skipped, provide a reason, ensuring traceability of decisions.
  • Output protocol: report a "Verified:" line with results and a "Not verified:" line with missing items and reasons.

Quick Start

Run ship-check after a change to obtain a minimal, credible verification report.

Frequently Asked Questions about ship-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run smoke tests and code verification checks after a code change?▼

ship-check identifies changes across code, configuration, documentation, and tests, then verifies them with the smallest credible verification set. It applies targeted checks in order: syntax/parse, typecheck/lint, focused tests, and runtime smoke tests.

How do I verify code changes without running the entire test suite?▼

To verify changes without running everything, ship-check runs only the smallest credible verification set. It applies targeted checks sequentially and reports which stronger checks were skipped with clear reasons for traceability.

What is the correct order for running syntax, typecheck, and smoke tests?▼

The correct order for verification checks is syntax/parse first, followed by typecheck/lint, then focused tests, and finally runtime smoke tests. This sequence ensures basic errors are caught before deeper execution.

Can I verify configuration and documentation changes alongside code modifications?▼

Yes, ship-check identifies changes across code, configuration, documentation, and tests. It verifies all these modified files using the targeted checking sequence to ensure comprehensive validation of your project.

How do I get a traceable report of which verification checks passed or were skipped?▼

ship-check provides a clear output protocol by reporting a "Verified:" line with passing results and a "Not verified:" line with missing items and reasons. This ensures full traceability of your verification decisions.

Related Skills

Explore More Software Engineering Skills→
iamcxaiamcxa
3

e2e-doc-sync

Syncs changed E2E plugin source files with documentation to detect gaps via diff-aware inventory and live probe verification.

Community
Advanced
masakinihirotamasakinihirota

release-workflow

Manage secure code releases to the main branch with validation and versioning.

Community
Advanced
0xHoneyJar0xHoneyJar
1

dapp-test

Run Web3 dApp test suites with Vitest, Jest, or Bun and analyze failures.

Official
Advanced
Hack23Hack23
235

unit-testing-patterns

Write JUnit 5 unit tests with Mockito and AssertJ for CIA platform services.

Official
Basic