ship-wreck-check

Review changed files and run quality checks before shipping.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/its-meseba/meseba-skills --skill ship-wreck-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-wreck-check
Source: https://github.com/its-meseba/meseba-skills/tree/main/skills/ship-wreck-check
Command: npx skills add https://github.com/its-meseba/meseba-skills --skill ship-wreck-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a brutal, pre-release quality review of completed work to catch defects and risks before shipping.

Core Features & Use Cases

  • Gather all changed files (uncommitted, unpushed, and branch diff)
  • Discover project quality commands (lint, build, tests, etc.)
  • Run ALL quality commands and ensure they pass
  • Intent verification and alignment with the planned work
  • Deep review of changed files and related context
  • Invoke the code-simplifier to surface simplifications
  • Report findings with precise file:line references and actionable fixes

Quick Start

Run the Ship-Wreck-Check after completing a feature, bugfix, or refactor to perform a brutal pre-ship quality review.

Frequently Asked Questions about ship-wreck-check

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

FAQPage Schema
How do I perform a pre-release quality review on uncommitted code changes?

To perform a pre-release quality review, gather all uncommitted, unpushed, and branch-diff files, discover project quality commands, and run every lint, build, and test check to ensure production safety before shipping.

What is brutal code review for production safety?

Brutal code review is a rigorous pre-ship assessment that uncovers defects, gaps, and risks in completed features or bug fixes by verifying intent, performing deep reviews, and reporting with precise file:line references.

How do I detect defects in a branch before merging to production?

Detect defects by running all project quality commands, verifying alignment with planned work, and performing a deep review of changed files and related context to surface risks before merging.

Can I use a code-simplifier during a pre-ship defect detection process?

Yes, a pre-ship defect detection process can invoke a code-simplifier to surface simplifications, ensuring the completed work is both safe for production and structurally optimized before shipping.

What is the best way to verify code intent aligns with planned work before shipping?

The best way to verify code intent is to perform intent verification against the planned work, run all quality commands, and execute a deep review of changed files to ensure alignment before shipping.

Does a brutal quality review report actionable fixes for detected defects?

Yes, a brutal quality review reports findings with precise file:line references and actionable fixes, ensuring developers can immediately address uncovered defects, gaps, and risks before release.