skills.rest
furrycolombia-sys
furrycolombia-sysCOMMUNITY
Explore all skills by this author →
GitHub

create-release

Merge develop into main via pull request and generate release notes.

1|Updated Mar 18, 2026
Search Tags:#automation#git#changelog#release#pull-request
One-click install
npx skills add https://github.com/furrycolombia-sys/candyshop --skill create-release-furrycolombia-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-release
Source: https://github.com/furrycolombia-sys/candyshop/tree/main/.agents/skills/create-release
Command: npx skills add https://github.com/furrycolombia-sys/candyshop --skill create-release-furrycolombia-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates production releases by merging the develop branch into main through a pull request and generating release notes, ensuring a consistent, auditable release process.

Core Features & Use Cases

  • Automates PR-based merges from develop to main.
  • Generates release notes for the new version and attaches them to the PR or release entry.
  • Enforces reading the Claude workflow source to align with organizational standards.

Quick Start

Automatically merge develop into main via a PR and generate release notes for the new release.

Frequently Asked Questions about create-release

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

FAQPage Schema
How do I automate merging develop into main through a pull request?▼

Automating production releases involves merging the develop branch into main via a pull request. This skill executes that PR-based merge while generating release notes, ensuring a consistent and auditable Git branch workflow.

Can I automatically generate release notes and changelogs for a new Git version?▼

Yes, generating release notes for a new version is supported. The skill creates changelog content and attaches it directly to the pull request or release entry during the develop to main merge.

What is the best way to enforce traceable PR-based merges for production releases?▼

Traceable PR-based merges are enforced by routing develop to main through a pull request. This approach guarantees an auditable release process with attached release notes for organizational standard compliance.

Do I need specific Git branch configurations to automate production releases?▼

Automating production releases requires a Git repository with active develop and main branches. The workflow merges develop into main through a pull request, generating release notes for the new version.

When should I use an automated PR merge for Git release workflows?▼

An automated PR merge for Git release workflows is needed when you require traceable merges from develop to main. It suits software release processes that need generated release notes and an auditable changelog history.

Related Skills

Explore More Software Engineering Skills→
dnvitidnviti
11

git-publish

Merge develop into main and push both branches to origin.

Community
Intermediate
masx200masx200
2

github-release

Create GitHub releases from tagged commits using gh CLI.

Community
Advanced
wangfeivwangfeiv

gstack/ship

Automate code integration, testing, versioning, changelog generation, and pull request creation.

Community
Advanced
a29paula29paul
1

ship

Automate code shipping with base branch detection, tests, version bumping, and PR creation.

Community
Advanced