release

Automate version increments and generate bilingual release notes via git.

3|1|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/caterpi11ar/locusify --skill release-caterpi11ar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/caterpi11ar/locusify/tree/main/packages/app/.agents/skills/release
Command: npx skills add https://github.com/caterpi11ar/locusify --skill release-caterpi11ar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual overhead of managing software releases, ensuring consistent versioning and high-quality, bilingual documentation without repetitive copy-pasting.

Core Features & Use Cases

  • Automated Versioning: Calculates and updates version numbers in package.json based on user input.
  • Bilingual Documentation: Automatically generates structured release notes in both English and Chinese.
  • CI/CD Integration: Streamlines the release lifecycle by creating git tags and triggering deployment workflows.

Quick Start

Ask the release skill to bump the version and generate the release notes for the latest changes.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumps and generate release notes from git commits?

You can automate version bumps and release note generation by integrating git with package.json. This workflow calculates version increments, updates the package file, and creates structured documentation for your latest changes.

Can I automatically generate bilingual release notes in English and Chinese?

Yes, you can generate bilingual release notes in English and Chinese. The automation produces structured documentation for both languages simultaneously, eliminating manual translation and repetitive copy-pasting during your release process.

Does automated versioning require git integration and access to package.json?

Automated versioning requires both git integration and access to package.json. These dependencies are essential for calculating version increments, updating version numbers, and creating git tags to trigger CI/CD deployment workflows.

What's the best way to streamline a software release lifecycle with CI/CD integration?

Streamline a software release lifecycle by automating version increments, documentation, and git tag creation. This approach synchronizes package updates with deployment workflows, reducing manual overhead while maintaining consistent release documentation.

How do I create git tags for new package versions automatically?

Create git tags for new package versions automatically by running a release automation workflow. The system updates your version number in package.json and then creates the corresponding git tag to mark the release point.

Why does manual release management cause inconsistent versioning and documentation overhead?

Manual release management causes inconsistent versioning and documentation overhead due to repetitive copy-pasting and human error. Automating version increments and bilingual release notes ensures consistent updates without the manual overhead.