What problem does it solve? Merging code without verifying quality gates leads to broken builds, failing tests, and unmet requirements on the main branch. This Skill enforces a consistent pre-merge checklist so every branch is validated before it ships. ## Core Features & Use Cases - Technical Checks: Runs typecheck, lint, and test commands defined in your project's tech-stack configuration and reports PASS/FAIL for each. - Code Review: Diffs the current branch against main and checks changes against coding standards, security, and performance rules. - Task Tracking & Definition of Done: Verifies the task is marked complete in the sprint file and validates acceptance criteria when a task ID is provided. - Use Case: Before merging a feature branch, run the checklist to confirm zero type errors, zero lint warnings, passing tests, and verified acceptance criteria, then get a clear READY TO MERGE or NOT READY verdict with next steps. ## Quick Start Ask the AI to ship the current task by running the pre-merge checklist for this branch before merging.