What problem does it solve? Determining whether a change, branch, or PR is truly ready to review, merge, ship, or hand off requires gathering scattered evidence from local gates, CI, IDE inspections, and browser checks. This Skill consolidates that evidence into a single truthful readiness verdict with explicit blockers and next actions. ## Core Features & Use Cases - Gate Orchestration: Reads .github/github.json quality gates and repo instructions to decide which tests, lint, typechecks, builds, and inspections must run for the changed surface. - Evidence Aggregation: Delegates to focused skills for JetBrains inspections, GitHub PR/CI state, browser UI validation, and security review, then merges results into one report. - Structured Readiness Report: Returns status (ready, not ready, partially ready, blocked) with passed, failed, pending, and not-run evidence plus the smallest next action. - Use Case: Before merging a feature branch, ask whether the PR is ready; the Skill checks local git state, runs required gates, verifies CI and review status, and reports any blockers with concrete reasons. ## Quick Start Use the repo-readiness skill to check whether my current branch is ready to merge and report the gate evidence.
