git-release

Automate Git release workflows for Node.js projects with package.json.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/chogng/Skills --skill git-release-chogng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-release
Source: https://github.com/chogng/Skills/tree/main/git-release
Command: npx skills add https://github.com/chogng/Skills --skill git-release-chogng

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Git teams face inconsistent, error-prone release processes that miss steps like committing all changes, bumping versions, generating changelogs, and pushing tags. This Skill automates the entire Git release lifecycle to ensure every release is complete, auditable, and repeatable across projects.

Core Features & Use Cases

  • Full-release automation: triggers on release keywords and executes the complete sequence: commit, bump version, create tag, and push.
  • Version synchronization: updates version numbers in package.json (and server/package.json if present) to keep multi-package repos consistent.
  • Safe, auditable workflow: enforces full-flow execution, logs actions, and prompts for release type when required.

Quick Start

Trigger the full release workflow by saying a release keyword such as 更新版本, 发布版本, or bump version.

Frequently Asked Questions about git-release

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

FAQPage Schema
How do I automate a full Git release workflow including version bumping and tagging?

To automate a Git release workflow, this Skill coordinates commits, semantic version bumps, tag creation, and pushes to remote repositories. You trigger the sequence using release keywords like bump version, then specify the release type as patch, minor, or major.

Can I synchronize version numbers across multiple package.json files during a Git release?

Yes, this Skill synchronizes version numbers across multiple package.json files during a Git release. It automatically updates the root package.json and the server/package.json file if present, ensuring multi-package repositories remain consistent.

Does this Git release automation tool support projects without a package.json?

No, this Git release automation tool targets Node.js projects and requires a package.json file to execute the version bump workflow. It relies on the package.json structure to update version numbers and maintain multi-package synchronization.

What is the best way to ensure a Git release is auditable and repeatable across projects?

The best way to ensure an auditable and repeatable Git release is to enforce full-flow execution that logs actions. This Skill automates the entire lifecycle from code changes to tag publication, preventing missed steps and inconsistent releases.

How do I specify a major, minor, or patch version bump when publishing a release?

To specify a major, minor, or patch version bump when publishing a release, you simply interact with the prompt after triggering the workflow. The Skill requires you to confirm the release type and scope of changes before proceeding with the version update.