release
Prepare a guarded release of hacs_waste_collection_schedule. Use when a maintainer asks for the next release, a target version, changelog drafting, a manifest bump, or a release pull request.
77
Quality
96%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Low
Low-risk findings worth noting
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.
- Repository
- mampfes/hacs_waste_collection_schedule
- Commit
82a9f36
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.