cut-releaselisted

# Cut a Release Take a repository from "the work is committed" to "the version is published and verified". One command covers every repository whose release differs only in which optional steps apply: screenshots, a pull request, an automated release workflow, a package publish. The skill probes for each capability rather than being told, so the same invocation is correct in a headless CLI and in a full web app. Invoking this skill authorizes its commit, push, tag, release, and publish steps. ## Usage ``` cut-release [repo-path] [--dry-run] ``` `--dry-run` runs Phase 0 and prints the plan, then stops. Nothing is written, pushed, or tagged. ## Out of scope - **The Spernakit template.** It releases through `spernakit-bump`, which the dance drives. Abort if the repository is the template. - **Spernakit-derived apps.** Their `package.json` carries a `spernakit_version` origin marker; they are bumped and tagged by the dance's D3 phase against the template version they synced from. Abort and say so — cutting one by hand outside a dance detaches it from its propagation record. Everything else with a version manifest and a git remote is in scope. ## Phase 0 - Preflight and capability probe Collect every fact first, print the resulting plan, then execute it. A probe that errors is not a "no"; resolve it before continuing. ### Identity ```text git rev-parse --show-toplevel git branch --show-current git remote get-url origin gh auth status ``` Work from the toplevel.