release

Synchronize version numbers across project files and create Git tags.

3|1|Updated Jan 18, 2026

Search Tags:#automation #git #ci/cd #versioning #deployment #release

Ready to run

npx skills add https://github.com/madeinoz67/madeinoz-knowledge-system --skill release-madeinoz67

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/madeinoz67/madeinoz-knowledge-system/tree/main/.claude/skills/release
Command: npx skills add https://github.com/madeinoz67/madeinoz-knowledge-system --skill release-madeinoz67

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of releasing new versions of software, ensuring consistency and triggering necessary workflows.

Core Features & Use Cases

Version Synchronization: Updates version numbers across multiple critical files (package.json, Dockerfile, README.md, SKILL.md, docker-compose-production.yml).
Git Tagging & Pushing: Creates annotated Git tags and pushes them to trigger CI/CD pipelines.
Use Case: When preparing to launch version 2.0.0 of your project, use this skill to update all version indicators, create a v2.0.0 tag, and push it to GitHub, automatically initiating the build, test, and deployment pipeline.

Quick Start

Use the release skill to bump the version to 1.9.0 and create a git tag.

Frequently Asked Questions about release

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

FAQPage Schema

How do I synchronize version numbers across multiple files for a release?▼

To synchronize version numbers during a release, this Skill automatically updates package.json, Dockerfile, README.md, SKILL.md, and docker-compose-production.yml to ensure consistency across your project before tagging.

How do I create a Git tag and push it to trigger CI/CD pipelines?▼

You can trigger CI/CD pipelines by using this Skill to create an annotated Git tag for the new release version and push it directly to your remote repository, initiating downstream workflows.

What is the best way to automate deployment versioning in Docker and Node.js projects?▼

Automating deployment versioning in Docker and Node.js projects is handled by updating version indicators across package.json, Dockerfile, and docker-compose-production.yml, then pushing a Git tag to start deployment.

Do I need to manually update my README and SKILL documentation when bumping a release version?▼

You do not need to manually update README.md or SKILL.md when bumping a release version, because this Skill automatically synchronizes the version numbers across those documentation files.

Can I use this release automation for projects without a docker-compose-production.yml file?▼

Using this release automation for projects without a docker-compose-production.yml file may cause synchronization errors, as the Skill is designed to explicitly update that file along with package.json and Dockerfile.