entwurf-release
SolidOperate entwurf SemVer releases through four explicit modes: land, prepare, make, and publish. Use for pre-version exact-SHA CI landing, CHANGELOG and package preparation, static and LIVE gates, prepared-HEAD CI, exact artifact acceptance, tag and GitHub release creation, repair-dist-tag publication, and post-publish registry proof. Each mode is a separate authority boundary. Triggers: release land, prepare-release, make-release, publish release, release cut, prerelease, repair release.
Install
Quality Score: 77/100
Skill Content
Details
- Author
- junghan0611
- Repository
- junghan0611/entwurf
- Created
- 3 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
release
Run a versioned release with git-flow discipline: deterministic preflight (branch, clean tree, Conventional Commits since last tag → suggested semver bump), changelog entry written from fragments/commits into the changelog file automatically, then the exact squash-merge/tag/push/GitHub-release sequence printed and consent-gated by default (configurable auto mode). Two configurable modes: light (dev → main) and full git-flow (release/* stabilization + hotfix/* branches). Use for 'release', 'cut a release', 'ship a version', 'bump the version', 'publish vX.Y.Z', 'hotfix production' — whenever accumulated work should become a tagged, published version.
release
Prepare a version release — bump version files, commit, and tag. Just run /release with no arguments.
release
Cut an ibkr release end-to-end with exactly one human stop. Autonomously preflights auth (verify-first Actions-OIDC), shared-tree state, version stamps, changelog, and gates; presents a findings-first GO/NO-GO; then fires and supervises `make release` and runs the full post-release verification (assets, tags, registry, fresh-clone build, live site stamps). Use when asked to cut, ship, prepare, or verify a release. Never tags, pushes, or creates GitHub releases directly; never force-pushes; never implements feature code in-release.