What problem does it solve?
Releasing Crowi involves human judgment that CI cannot automate: deciding when to cut a release and confirming that npm packages, Docker images, and GitHub Releases actually shipped. This Skill standardizes those two human-side tasks so nothing is merged, tagged, or published without explicit approval and evidence.
Core Features & Use Cases
- Pre-flight Go/No-Go report: Collects pending changesets, the open Version PR, main-branch CI status, commits since the last tag, unmerged worktrees, and a production-build smoke test into a single decision summary.
- Post-release verification: Read-only checks that the Release and Docker workflows succeeded, every public workspace package was published to npm, Docker images pull and run, and the GitHub Release notes exist.
- Manual fallback runbook: Step-by-step recovery path for publishing by hand when CI is broken, including Trusted Publisher and multi-arch buildx pitfalls.
- Use Case: Before merging the changesets Version PR, run the pre-flight mode to see exactly what ships, what is excluded, and whether main is green; after the tag, run verify mode to confirm all artifacts landed.
Quick Start
Ask the agent to run the crowi-release pre-flight check and present the Go/No-Go decision materials for the next release.