Automates the release lifecycle from commit analysis and version bumping to changelog updates and Git tagging.

Install

mkdir -p .claude/skills/release-bitsocialnet && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15435" && unzip -o skill.zip -d .claude/skills/release-bitsocialnet && rm skill.zip

Installs to .claude/skills/release-bitsocialnet

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Automate a full seedit release by analyzing commits, updating the release body, bumping the version, regenerating the changelog, and finalizing the git tag. Use when the user says "release", "new version", "cut a release", "prepare release", or provides a version number to ship.
279 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • →Analyze commits since the last tag
  • →Write a one-liner description for the release body
  • →Bump the version in `package.json` based on bump level
  • →Regenerate `CHANGELOG.md` from conventional commits
  • →Commit changes, create a git tag, and push to remote
  • →Perform a dry run of the release process

How it works

The skill automates the release process by analyzing commit history, updating version and changelog files, and then committing and tagging the release in git.

Inputs & outputs

You give it
A version bump level (patch, minor, major, or x.y.z) or a request to release
You get back
Updated `package.json`, `CHANGELOG.md`, and a new git tag pushed to remote

When to use release

  • →Cut a new release
  • →Bump version in package.json
  • →Generate automated changelog

About release

Analyzes commit history to generate release notes, updates package versions, creates changelogs, and pushes finalized release tags to the repository.

Automate a full seedit release by analyzing commits, updating the release body, bumping the version, regenerating the changelog, and finalizing the git tag. Use when the user says "release", "new version", "cut a release", "prepare release", or provides a version number to ship.

When not to use it

  • →When there are no new commits since the last tag
  • →When the user does not want to create a new release
  • →When the user wants to manually manage release artifacts

Limitations

  • →Requires conventional commits for changelog generation
  • →Requires `package.json` for version bumping
  • →Dry-run mode skips git operations

How it compares

This workflow automates the entire release process from commit analysis to git tagging, reducing manual steps and ensuring consistency compared to a manual release.

Compared to similar skills

release side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
release (this skill)04moReviewIntermediate
github-workflow-automation114moReviewAdvanced
testing-workflow1611moReviewIntermediate
github-actions-templates75moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

Search skills

Search the agent skills registry