Orchestrate semantic releases from develop to main with approval gates.
npx skills add https://github.com/usetheodev/theo-ui --skill release-usetheodev
Please help me install this Agent Skill. Skill: release Source: https://github.com/usetheodev/theo-ui/tree/main/.claude/skills/release Command: npx skills add https://github.com/usetheodev/theo-ui --skill release-usetheodev
The Release skill automates the end-to-end release workflow from development to production by deriving semantic versions from CHANGELOG sections, rewriting release notes, and orchestrating PRs and annotated tags with a mandatory human approval gate.
Run the release workflow after /review returns READY_TO_MERGE to initiate the cycle and follow the prompts.
High-intent search queries and answers about installing and using this skill.
To automate semantic releases with a human approval gate, this Skill orchestrates a full cycle from develop to main, opening a PR with rendered release notes and waiting for manual merge before creating an annotated tag and GitHub release.
Deriving the next version from a CHANGELOG works by reading the Unreleased section using Keep-a-Changelog rules, calculating the semantic version bump, and rewriting the Unreleased section under the new version header with a fresh Unreleased section at the top.
Yes, you can use PR-based governance for semantic versioning across develop and main branches, as this Skill opens a release PR containing rendered notes and only creates the annotated tag and GitHub release upon human approval and merge.
The best way to generate release notes and record metadata is to automatically render the Unreleased CHANGELOG entries into the release PR, then create an annotated tag and GitHub release on merge to permanently record the release metadata.
Yes, you need a Git workflow relying on develop and main branches with a CHANGELOG file to automate semantic releases, as the Skill derives versions from Unreleased sections and promotes code via PRs across this specific branch structure.
You should not use an automated semantic release cycle if your Git workflow lacks a CHANGELOG file, does not follow develop-to-main branch promotion, or requires fully continuous deployment without a mandatory human approval gate.
jubscodesUpdate CHANGELOG.md from git history following Keep a Changelog format.
drvossAutomates version tagging, changelog generation, GitHub Releases, and artifact publishing to registries.
selfagencyAutomate semantic versioned GitHub releases with changelog PRs.
YanCheng-goAutomate branch creation, commits, PR review, and gated merge with human approval.
