pre-ship

Verify software development claims by running commands and validating output.

Updated Feb 22, 2026

Search Tags:#code quality #testing #ci/cd #commit #verification #quality gate

Ready to run

npx skills add https://github.com/jpeggdev/buildwithjpegg --skill pre-ship

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pre-ship
Source: https://github.com/jpeggdev/buildwithjpegg/tree/main/plugins/development-workflow/skills/pre-ship
Command: npx skills add https://github.com/jpeggdev/buildwithjpegg --skill pre-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the costly mistake of claiming work is complete, fixed, or passing without concrete evidence, thereby maintaining trust and preventing rework.

Core Features & Use Cases

Mandatory Verification: Enforces running specific commands to prove claims before any success assertion.
Evidence-Based Claims: Requires tangible output from verification commands as proof.
Use Case: Before committing code, you must run the test suite and confirm zero failures, providing the output as evidence of passing tests.

Quick Start

Use the pre-ship skill to verify that all tests are passing before claiming completion.

Frequently Asked Questions about pre-ship

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

FAQPage Schema

How do I enforce code verification before a commit?▼

To enforce code verification before a commit, you need a strict process that requires running testing, linting, and building commands, validating their output as evidence to confirm status before claiming completion.

What is a quality gate in CI/CD pipelines?▼

A quality gate in CI/CD pipelines is a mandatory verification step that prevents claiming task completion without concrete evidence, requiring successful command execution outputs like passing tests before proceeding.

How do I prevent claiming code is fixed without proof?▼

You prevent claiming code is fixed without proof by enforcing evidence-based assertions, requiring tangible output from verification commands like test suites to confirm zero failures before any success is declared.

Does mandatory verification work for bug fixing tasks?▼

Yes, mandatory verification works for bug fixing tasks. It applies to all stages of software development, requiring you to execute relevant commands and validate their output to confirm the bug fix status.

What is the best way to verify a test suite is passing?▼

The best way to verify a test suite is passing is to execute the relevant test commands and confirm zero failures by checking the tangible output provided as evidence before committing code.