che-ship

Run /che-ship once all tasks are marked DONE in the worktree. It executes the scope, code review, compliance, and QA gates first, then creates atomic conventional commits, pushes the branch, and opens a draft PR against the default branch assigned to you.

Five gates run in fail-fast order: scope-checker 6-checks (score ≥7.0), code review Mode B, a heavy full-repo compliance scan requiring 0 CRITICAL and 0 HIGH, a QA gate with minimal/normal/full profiles, and optional domain gates for non-engineering work.

Yes, but only when there are 0 CRITICAL and at most 2 HIGH findings. Auto-fixable HIGH findings are applied and committed with a conventional fix commit without asking the user. CRITICAL findings or 3+ HIGH findings block the ship and require manual fixes or logged overrides.

Only by passing --skip-qa together with an explicit written justification that is recorded in the decision log as an EXPLICIT_OVERRIDE entry. Without that logged override, the ship is blocked; there is no silent bypass path.

Yes. If an approved gh_stack_plan.md exists in the shared workspace and the gh-stack extension is installed, it ships layers bottom-up as a hierarchical PR stack. Otherwise it falls back to the standard single-PR path.

Ship requires a Level 1 session-to-worktree binding in the global registry, and the bound worktree must match the one being shipped. A mismatch or missing binding blocks the ship to prevent committing to the wrong worktree; you must confirm or rebind before continuing.