skills.rest
eretica
ereticaCOMMUNITY
Explore all skills by this author →
GitHub

build-and-release

Automate version bumping, commit, tag, and push to GitHub for releases.

Updated Jan 6, 2026
Search Tags:#automation#git#workflow#versioning#release#ci-cd#tagging
One-click install
npx skills add https://github.com/eretica/github-gh-reminder --skill build-and-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-and-release
Source: https://github.com/eretica/github-gh-reminder/tree/main/.claude/skills/build-and-release
Command: npx skills add https://github.com/eretica/github-gh-reminder --skill build-and-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end software release workflow: bumping version numbers, committing changes, creating tags, and pushing to GitHub to trigger CI/CD releases.

Core Features & Use Cases

  • Automated version bump: detect current version, update to a new version in package.json.
  • Git operations orchestration: commit changes, create lightweight tags, push to origin/main and tags.
  • Release triggering: pushes trigger GitHub Actions-based release pipelines.
  • Use case: When preparing a new software release, run this skill to ensure consistent versioning and remote publishing with minimal manual steps.

Quick Start

Run the release automation on a clean repository in the main branch to bump the version, commit, tag, and push.

Frequently Asked Questions about build-and-release

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

FAQPage Schema
How do I automate git version bumping, tagging, and pushing to trigger a release?▼

Automating git version bumping and pushing requires a clean working directory on the main branch with a properly configured package.json. The workflow bumps the version, commits with a conventional message, tags, and pushes to trigger CI/CD.

What is the best way to trigger GitHub Actions releases using git tags?▼

Triggering GitHub Actions releases using git tags is handled by pushing a newly created vX.Y.Z tag to your origin repository. This workflow orchestrates the end-to-end process of version bumping, committing, and tag pushing for you.

Do I need a clean working directory to run automated versioning and release workflows?▼

Yes, a clean working directory is required to run an automated versioning workflow. The process commits changes and creates tags on the main branch, so uncommitted local modifications will prevent a successful formal versioning release.

Can I use automated release tagging on a branch other than main?▼

No, automated release tagging is designed specifically for Git repositories on the main branch. It updates package.json and pushes commits and tags to origin/main to ensure consistent CI/CD release triggering.

What happens during an end-to-end automated git release workflow?▼

During an end-to-end automated git release workflow, the current version is detected and updated in package.json. The changes are then committed with a conventional message, a lightweight vX.Y.Z tag is created, and everything is pushed to origin.

Related Skills

Explore More Software Engineering Skills→
hiddink-aihiddink-ai
1

hiddink-harness:npm-version

Automate npm package version bumps, changelogs, and git tags.

Official
Intermediate
whilpwhilp
9

gh-workflow

Trigger and monitor GitHub Actions workflows via gh CLI.

Community
Advanced
FutureAtomsFutureAtoms
1

git-github-changelog

Generate and update changelogs in Keep a Changelog format from Git commit history.

Community
Intermediate
aussiegingersnapaussiegingersnap
9

versioning

Automate semantic versioning and changelog generation for Node.js projects using conventional commits.

Community
Advanced