pull-request-readylisted

# Pull request ready Turn a finished Backstage change into something a reviewer can approve: a diff that contains only the change, evidence the validation actually ran, and a PR body that answers the questions a reviewer would otherwise ask. ## Preconditions - The change is functionally complete. This skill does not write features. - A base branch exists and is fetched. `git fetch origin` first — everything below compares against `origin/<base>`, and Backstage's `--since` tooling silently checks nothing when the ref is missing. - Repository generation known (NFS vs legacy frontend, new vs legacy backend) so you can judge whether an import or wiring change is in-house style or an accidental regression. - Repository contribution surface detected, not assumed — see step 2. A `create-app` app repo has none of the publishing machinery that `backstage/backstage` and `backstage/community-plugins` have. - **You will not push, open, or merge anything.** Those require explicit authorization; this skill ends by handing back commands. ## Procedure 1. **Fix the base and read the real diff.** `BASE=$(git merge-base origin/<base> HEAD)`; review `git diff $BASE..HEAD` in full, plus `git status --porcelain` for anything uncommitted or untracked. Never self-review with `git diff HEAD~1` — it hides everything earlier on the branch. 2. **Detect what this repo requires.** Presence of `.changeset/config.json`; any `api-report*.md` at package roots or a `build:api-reports` script; root `packag