release

Automate Perry project releases by versioning, committing, tagging, and pushing to CI.

35|5|Updated Jan 1, 2026
One-click install
npx skills add https://github.com/gricha/perry --skill release-gricha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/gricha/perry/tree/main/.claude/skills/release
Command: npx skills add https://github.com/gricha/perry --skill release-gricha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing Perry projects requires manual steps like updating version, committing, tagging, and triggering CI; this skill automates that process, reducing error and time.

Core Features & Use Cases

  • Version bump in package.json and commit with a conventional message
  • Git tagging and pushing to trigger CI/CD pipelines
  • Lightweight release workflow suitable for small teams and solo maintainers

Quick Start

Run the release skill to cut a new Perry release and trigger CI publish.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate git tagging and version bumping for CI publish?

Automating git tagging and version bumping for CI publish involves reading package.json, incrementing the version, committing changes, creating a git tag, and pushing to trigger CI pipelines.

What is the best way to cut a new release across multi-environment pipelines?

Cutting a new release across multi-environment pipelines requires committing a version bump with a conventional message and pushing a git tag to trigger configured CI workflows, streamlining deployments for small teams and solo maintainers.

Do I need main branch access to automate version control and tagging?

Yes, automating version control and tagging requires access to the main branch. The workflow assumes you have main branch permissions to push git tags and trigger CI configurations across multi-environment pipelines.

Can I use this release workflow with package.json and CI configurations?

Yes, the release workflow works with package.json and CI configurations. It reads package.json to apply version increments and uses git to push tags, directly triggering your existing CI/CD pipelines for publishing.

Why does git tagging not trigger CI publish automatically?

Git tagging might not trigger CI publish if CI is not properly configured or if the tag is not pushed to the main branch. The release process assumes CI is already set up to respond to pushed tags.