release

Name: release
Availability: InStock
Author: Bitsocial

Automate Bitsocial Web release management from commit analysis to Git tagging.

1|1|Updated Feb 1, 2026

Search Tags:#automation #git #versioning #release #package.json #tagging #build-verification

Ready to run

npx skills add https://github.com/bitsocialnet/bitsocial-web --skill release-bitsocialnet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/bitsocialnet/bitsocial-web/tree/main/.cursor/skills/release
Command: npx skills add https://github.com/bitsocialnet/bitsocial-web --skill release-bitsocialnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end automation of Bitsocial Web release processes, reducing manual toil and human error during tagging, version bumps, and builds.

Core Features & Use Cases

Automates commit analysis to identify the latest release tag and changes since then
Bumps the version in package.json according to patch/minor/major or an explicit version
Verifies the release by running build and quality checks, then prepares commit, tag, and push steps

Quick Start

Specify a bump level (patch, minor, major, or an explicit version) to initiate the release workflow.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate version bumping and Git tagging for a release?▼

Automate version bumping and Git tagging by specifying a patch, minor, major, or explicit version to initiate the release workflow, which computes the new version, updates package.json, and performs the commit and tag operations.

What's the best way to prepare a new package release without manual toil?▼

The best way to prepare a new package release is using an automated workflow that analyzes commits since the latest tag, bumps the version in package.json, verifies the build, and handles the Git commit and push.

How does automated release management identify which version to publish?▼

Automated release management identifies the version to publish by reading the latest Git tag, analyzing subsequent commits, and computing the new version based on your specified patch, minor, major, or explicit version bump level.

Does the release workflow run build verification before tagging the commit?▼

Yes, the release workflow runs build and quality checks to verify the release before it prepares the commit, tag, and push steps, ensuring the tagged version is stable.

Can I specify an explicit version number instead of using patch, minor, or major bumps?▼

Yes, you can specify an explicit version number instead of relying on automated patch, minor, or major bumps to initiate the end-to-end release workflow and update package.json accordingly.

When do I need to run an end-to-end release workflow instead of manual tagging?▼

You need an end-to-end release workflow when preparing a new release containing version bumps, as it reduces human error during build verification, package.json updates, and Git tagging operations.