Does this skill automatically create a GitHub Pull Request?

No, this skill is designed to prepare the branch and push changes. PR creation is intentionally left to automated tools like GitHub Actions to maintain a clean separation of concerns.

What happens if my local branch is out of sync?

The skill performs a preflight check using git fetch and status. If your local branch is behind origin, it will prompt you to pull the latest changes before proceeding.

Can I trigger this skill accidentally?

No, the skill is configured to only execute upon explicit user instructions such as 'release prepare' or 'release version X.Y.Z' to prevent accidental production changes.

What versioning standard does the skill support?

The skill follows Semantic Versioning (SemVer) standards, requiring the X.Y.Z format for all release preparations.

How does it handle the CHANGELOG.md file?

It identifies the 'Unreleased' section, renames it to the current version and date, updates comparison links, and inserts a fresh 'Unreleased' placeholder at the top.

Release Prepare Workflow

Name: Release Prepare Workflow
Author: no-problem-dev

byno-problem-dev

•

배포 및 DevOps

Automates standardized release preparation including CHANGELOG updates, version validation, and git synchronization.

The Release Prepare skill streamlines the critical pre-release phase of software development by managing documentation updates and git workflows. It guides Claude through a rigorous 6-step process that includes preflight checks to ensure remote synchronization, semantic version validation, and automated CHANGELOG.md management. By handling the transition from 'Unreleased' sections to versioned entries and performing automated pushes to release branches, it ensures consistency and prevents manual errors before CI/CD pipelines take over.

주요 기능

01Automated CHANGELOG.md updates including version header conversion and link updates

02Rigorous preflight checks to ensure local and remote git states are synchronized

03Smart detection of uncommitted changes and branch naming conflicts

044 GitHub stars

05Semantic versioning (SemVer) validation for consistent release tagging

06Automatic staging, committing, and pushing to specific release branches

사용 사례

01Ensuring release branches are perfectly synchronized with the remote before triggering CI/CD

02Standardizing the release process across a development team to ensure documentation consistency

03Automating the repetitive git and file editing tasks required before cutting a new release

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add no-problem-dev/claude-code-plugins release-prepare

For use in Claude.ai and ChatGPT

Download Skill