What problem does it solve? It prevents developers from declaring a Linear issue done prematurely by enforcing a quality gate: tests must pass, coverage gaps and code issues must be reviewed, a PR must be created, and CI must be green before completion. ## Core Features & Use Cases - Repo-aware test execution: Runs the correct test and lint commands per repository (pytest, xcodebuild, gradlew, supabase lint, maestro). - Agent-driven review chain: Dispatches testing-strategist, code-reviewer, and optionally e2e-qa-automation subagents to catch coverage gaps, security issues, and E2E needs. - PR and CI enforcement: Creates a structured GitHub PR with test plan and Closes AMA-NNN, then watches CI runs and distinguishes real failures from transient infrastructure crashes. - Use Case: After finishing work on Linear issue AMA-653 in chat-api, invoke the skill to run pytest, get a review, open the PR, and confirm all GitHub checks pass before closing the ticket. ## Quick Start Invoke the skill with the Linear issue ID, for example /finish-issue AMA-653, while on the feature branch for that issue.