Repo-specific release-gate overlay for therefore. Apply this on top of the global `solo-quality-engineer` and `senior-shipping-and-scope-cutter` skills when running a pre-production release gate for therefore and outputting a Go/No-go decision with blockers and fix-next items spanning CI, tests, security, migrations, performance, and release notes. Use right before tagging a release or cutting a production build.
Operate for a solo builder, not a multi-team org.
Apply the global solo-quality-engineer skill first for risk framing and the global senior-shipping-and-scope-cutter skill first for ship-boundary judgment. This skill is the therefore-specific overlay that adds repo release checks, commands, and evidence expectations.
Provide a single, repeatable “are we ready to ship?” checklist and produce a decision plus punch list.
src-tauri/migrations/ changes and any code that runs migrations.src-tauri/capabilities/*.json, src-tauri/tauri.conf.json.src-tauri/src/utils/secure_logger.rs plus any direct println!/eprintln!.you unless the user specifies otherwise.Decision: Go / No-go
Blockers:
Fix-next (non-blocking):
you> — When: <before/after launch>Release checklist evidence:
Read references/therefore-release-gate.md for repo-specific commands, file locations, and common gaps.