Analyze changes since the last tag, propose semver bumps, draft changelogs, and push git tags.
npx skills add https://github.com/rnwolfe/forge --skill release-rnwolfe
Please help me install this Agent Skill. Skill: release Source: https://github.com/rnwolfe/forge/tree/main/.claude/skills/release Command: npx skills add https://github.com/rnwolfe/forge --skill release-rnwolfe
Release management is often tedious and error-prone. This Skill automates end-to-end release tasks, including analyzing work since the last tag, proposing a semver bump, drafting a CHANGELOG entry, and tagging/pushing to trigger the release pipeline.
Run the release flow to start the end-to-end process and follow prompts.
High-intent search queries and answers about installing and using this skill.
Automate git release workflow by analyzing changes since the last tag, proposing semantic version bumps, drafting CHANGELOG entries, and pushing git tags. This end-to-end release process requires a forge.toml configuration file to guide the automated versioning and tagging workflow across multiple merged PRs.
Drafting a CHANGELOG from conventional commits involves categorizing unreleased changes since the last git tag, proposing a semver bump, and generating user-facing entries. This release automation categorizes merged PR changes to produce a structured changelog and guide the subsequent git tagging and pushing workflow.
Determine the correct semver bump by analyzing all unreleased changes and merged PRs since the last git tag. The release automation categorizes these changes to propose a version bump, draft a matching CHANGELOG entry, and guide the tagging and pushing workflow to trigger the release pipeline.
Yes, you need a forge.toml configuration file to automate software releases with this workflow. The release process reads project config from forge.toml to analyze changes, categorize commits, propose semver versions, draft changelogs, and guide the git tagging and pushing workflow across unreleased changes.
Yes, you can analyze changes since the last git tag and push tags automatically. The release workflow reads project config, categorizes unreleased changes from merged PRs, proposes a semver bump, drafts a CHANGELOG, and creates and pushes git tags to trigger the release pipeline.
Limitations of automating release management include dependency on a forge.toml configuration file and a conventional release process. This workflow analyzes changes since the last tag across merged PRs, but projects lacking conventional commit structures or forge.toml setup cannot utilize the automated semver and changelog drafting.
74nu5Generate conventional commit messages from diffs and stage files.
drvossAutomates version tagging, changelog generation, GitHub Releases, and artifact publishing to registries.
markus41Manage Git branching, commits, rebasing, and pull requests.
pacaplanCreate release pull requests with semantic version bumps and changelog entries.
