pre-ship-pipeline

Orchestrates code review, design, performance, and polish audits into one pre-merge quality pipeline.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1 --skill pre-ship-pipeline-joyjoin-tech-limited
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-ship-pipeline
Source: https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1/tree/main/.github/skills/pre-ship-pipeline
Command: npx skills add https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1 --skill pre-ship-pipeline-joyjoin-tech-limited

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running code review, review swarms, design audits, performance checks, and polish passes separately before shipping is slow and produces five redundant interview rounds. This Skill sequences the existing audit skills in the correct order, hands off between them, and collapses their separate grill-me interviews into one consolidated end-of-pipeline stress-test. ## Core Features & Use Cases - Ordered quality chain: Runs code review, post-implementation review swarm, UI layout/design/completeness audits, performance audit, fix loop, and polish in a defined sequence with clear gates. - Consolidated stress-test: Replaces five per-skill grill-me interviews with a single six-question cross-domain review before shipping. - Severity-disciplined fix loop: Only BLOCKING, P0, or Class A correctness findings trigger fixes; CONCERN and NIT items are logged without blocking. - Use Case: Before merging a PR for a new mini-program onboarding flow, run the full pipeline to get a swarm verdict, completeness score, performance gate, and a green harness gate in one pass. ## Quick Start Ask the AI to run the pre-ship pipeline on your current change before merging the PR.

Frequently Asked Questions about pre-ship-pipeline

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

FAQPage Schema
How do I run a full quality review before merging a PR?

Invoke the pre-ship pipeline, which sequences code review, a post-implementation review swarm, design and performance audits, a fix loop, and polish in order. It ends with a single consolidated stress-test and a green harness gate before the change is declared done.

What is the difference between the pre-ship pipeline and running each audit skill separately?

The pipeline owns only the ordering and handoff between the existing audit skills, not the audits themselves. Its main advantage is replacing five separate grill-me interviews with one consolidated cross-domain stress-test.

When should I not use the pre-ship pipeline?

Skip it for one-line typo fixes, where only the harness completion gate is needed, and when a single-skill audit suffices. Backend-only changes also skip the design, performance, and polish steps.

Which findings block a merge in the pre-ship pipeline?

Only BLOCKING, P0, and Class A correctness findings trigger a fix loop and block shipping. CONCERN, craft, and NIT findings are logged but remain non-blocking, matching the severity discipline of the review swarm.

What happens when audit skills give conflicting verdicts?

The stricter gate wins when verdicts conflict, such as a swarm PASS alongside a Class A design defect. Class A correctness issues always block regardless of other passing results.