What problem does it solve?
Advisory code quality scorecards often fail to prevent unshippable code from being merged into production, leading to security vulnerabilities, poor user experience, and costly post-deployment fixes. This Skill turns the /ship scorecard from a passive advisory into a blocking, deterministic quality gate that enforces minimum quality standards before code can be merged.
Core Features & Use Cases
- Configurable Thresholds: Set per-category minimum scores (e.g., 90 for security, 80 for accessibility) and overall pass bars tailored to your project type.
- Hard Failure Rules: Automatically block merges if leaked secrets or critical-severity audit findings are detected, regardless of overall score.
- CI & Pre-Push Integration: Wire the gate directly into your GitHub Actions workflows and local git pre-push hooks to enforce quality standards automatically for every commit and PR.
- Use Case: An engineering team can configure the gate to require a minimum overall ship score of 85, block any PR with leaked API keys, and run automatically in CI to ensure no low-quality or insecure code reaches production.
Quick Start
Use the ship-gate skill to initialize a blocking quality gate for your project that enforces minimum ship-readiness scores and blocks merges for code with critical issues or leaked secrets.
