mampfes Prepare a release
- Parse an optional target version from the user's request.
- Spawn the
release-managercustom agent. Ask it to inspect merged PRs, determine or validate the semantic version, and return the complete CHANGELOG section, manifest change, and GitHub release-notes body. - Do not let the agent create a branch, commit, push, tag, release, or PR during the draft phase.
- Present every draft verbatim with the bump rationale and ask the user for explicit approval.
- If the user requests changes, send them to the same agent and re-present the revised drafts.
- Only after explicit approval, send the agent:
Proceed with the approved release PR exactly as drafted. Prefix any approved mutating gh command with WCS_GITHUB_APPROVED=1. - Present the release PR URL and exact post-merge tag/release commands. Never create the tag or publish the GitHub release.