release

name	release
description	Use when preparing SemVer, changelog, release PRs, protected branches, deployment, or production readiness evidence.

Release Skill

Release policy

• Conventional Commits drive SemVer.
• development integrates verified work.
• main receives release PRs only.
• CI must pass before merge.
• Changelog/version generated by Python Semantic Release.
• The current workflow is release-readiness only until real publishing is explicitly enabled.
• Release tags must map to deployable commits.
• Use the repo readiness check before enabling publishing: npm run release:check.

If the task moves from release governance into the actual Render deployment path, use the installed $render-deploy skill alongside this one.

Output

• Release type:
• Commits included:
• Version impact:
• Changelog impact:
• Deployment checks:
• Rollback notes: