releasing

Name: releasing
Availability: InStock
Author: Dayopt

Automate version selection, duplicate checks, release notes, and tagging in PR-based release workflows.

Updated Jun 23, 2025

Search Tags:#automation #versioning #release #ci-cd #tagging #release-notes #pr-workflow

Ready to run

npx skills add https://github.com/Dayopt/app --skill releasing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: releasing
Source: https://github.com/Dayopt/app/tree/main/.claude/skills/releasing
Command: npx skills add https://github.com/Dayopt/app --skill releasing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, npm, and includes scripts (resource) components.

What problem does it solve?

This skill guides and enforces end-to-end release workflows for Dayopt projects, covering version decision, duplicate checks, release notes creation, and tagging to ensure safe, reproducible releases.

Core Features & Use Cases

Phase-driven release protocol (Phase 0 to Phase 3) that structures tasks from version decision to tagging.
Automated validation steps including duplicate checks, lint/typecheck/test/build, and package.json updates, plus generation of release notes.
Script-based tooling to fetch merged PRs and prepare release documentation, ensuring traceability.

Quick Start

Use the release skill to plan and execute versioning, release notes, and tagging in your PR workflow.

Frequently Asked Questions about releasing

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

FAQPage Schema

How do I automate version selection and release tagging in a PR workflow?▼

Automating release tagging in a PR workflow requires a phase-driven protocol that validates merged PRs, updates package.json, and creates traceable git tags on main branches to ensure safe, reproducible versioning.

What's the best way to prevent duplicate version numbers during a release?▼

Preventing duplicate version numbers involves enforcing automated duplicate checks before versioning, validating the proposed release tag against existing git tags to ensure no conflicts occur during the release cycle.

How do I generate release notes automatically from merged pull requests?▼

Generating release notes from merged pull requests uses script-based tooling to fetch merged PRs, extract traceable changes, and prepare structured release documentation as part of an end-to-end release workflow.

Do I need gh and jq installed to automate end-to-end release workflows?▼

Automating end-to-end release workflows requires gh, jq, git, and npm installed in your environment to fetch merged PRs, parse JSON outputs, manage repository tags, and update package.json version fields.

What validation steps should a safe release workflow include before tagging?▼

A safe release workflow should include duplicate version checks, lint, typecheck, test, and build validations, plus package.json updates, ensuring codebase stability before creating final git tags.

How do I structure a phase-driven release protocol for consistent versioning?▼

Structuring a phase-driven release protocol involves defining sequential phases from version decision to tagging, automating validation, release notes generation, and tag creation to achieve consistent and traceable releases.