merge-readinesslisted

# Merge Readiness ## Core Question Is this branch ready to merge, and which blockers, warnings, or evidence gaps remain? ## When To Use Use this skill when: - the user asks whether a branch is ready to merge - pre-merge blockers need to be listed - CI, tests, conflicts, changelog, or release requirements need a readiness verdict - the user wants merge risks without performing the merge ## When Not To Use Do not use this skill when: - performing the merge - approving or bypassing review controls - pushing branches or tags - resolving conflicts Route to: - PR summary routes to `pr-review-prep` - generic checks route to `preflight-checks` - branch sync issues route to `sync-branch` - conflicts route to `resolve-conflicts` ## Required Evidence Before action, inspect or establish: - status and branch relationship to target - merge-base and conflict likelihood where available - local verification results - CI or review evidence when available - changelog/release/version indicators - open blockers from diff risk No-evidence rule: - Do not make strong claims without observed evidence. - State assumptions when proceeding under incomplete evidence. - Stop when missing evidence affects safety, correctness, user work, remote state, or irreversible action. ## Operating Contract You MAY: - inspect relevant repository state and project files. - generate a plan, report, or local artifact within the declared risk scope. - route to another skill when the requested action is o