Cut and publish project releases from validated change sets.
npx skills add https://github.com/xtrm-dev/specialists --skill releasing-xtrm-dev
Please help me install this Agent Skill. Skill: releasing Source: https://github.com/xtrm-dev/specialists/tree/main/config/skills/releasing Command: npx skills add https://github.com/xtrm-dev/specialists --skill releasing-xtrm-dev
This Skill removes the manual friction of cutting a release by coordinating version bumps, changelog updates, build regeneration, tagging, pushing, and optional GitHub publication in one controlled flow.
Ask the assistant to cut the next release for the project, using the latest tag as the base and returning the final version, commit, tag, and push status.
High-intent search queries and answers about installing and using this skill.
Automating git tagging and changelog updates involves coordinating version bumps in package.json, drafting changelog entries, regenerating builds, tagging, and pushing in one controlled release flow. This ensures all release files are updated together without manual friction.
Cutting a semver release from a validated change set applies a strict release scope over CHANGELOG.md, package.json, and dist/. It verifies the final diff, version tag, and push status to ensure only approved files are modified during the release process.
No, the release orchestration process enforces strict file boundaries and does not modify source files. It limits its scope to CHANGELOG.md, package.json, and dist/, ensuring the release only touches approved output and metadata files.
Yes, you can publish an optional GitHub release and push git tags simultaneously. The release flow handles version bumping, changelog drafting, tagging, and pushing, while verifying that the tag and push operations completed successfully.
Drafting release notes from recent reports synthesizes changelog entries from recent activity before applying the version bump. This keeps the release scope limited to approved files while preparing the documentation for the final tag and push.
Enforcing strict release file boundaries limits modifications to CHANGELOG.md, package.json, and dist/. This means any source code changes or unapproved file modifications must be handled separately before the release orchestration begins.
girijashankarjAutomate version bumps, changelog generation, and Git tag releases.
computerlovetechCoordinate version bumps, changelog updates, quality checks, and tagging for agr releases.
ConductionNLCompare branch and origin/main VERSION files to validate semver bumps.
coreindustriesTag new versions, generate changelogs from conventional commits, and create GitHub releases.
