Pre-Ship Quality Review FAQs

Question 1

When should I use the Pre-Ship Review skill?

Accepted Answer

It is best used before any significant code shipment, such as opening a PR with multiple modules, preparing a release, or reaching a milestone that requires a quality gate pass.

Question 2

How does this differ from a standard CI/CD pipeline?

Accepted Answer

Unlike standard CI, this skill provides AI-assisted judgment on intent, architectural fitness, and domain correctness—complex checks that traditional automated pipelines typically cannot perform.

Question 3

What are integration boundary failures?

Accepted Answer

Integration boundary failures occur where separate components meet. Examples include mismatched function signatures, inconsistent constants across files, or broken architectural contracts that isolated unit tests might miss.

Question 4

Is this skill limited to Python projects?

Accepted Answer

The core logic and many orchestrated skills are polyglot. While some Phase 1 tools like Pyright are Python-specific, the manual judgment phase and many secondary skills apply to any programming language.

Question 5

Do I need to install external tools to use this skill?

Accepted Answer

While the skill works best with tools like Pyright, Vulture, and Semgrep, it features graceful degradation and will continue with other checks even if specific external tools are missing.

Pre-Ship Quality Review

主要功能

使用场景

Pre-Ship Quality Review

主要功能

使用场景