release-epic

Create a GitHub release pull request after verifying all child issues are closed.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill release-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-epic
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/release-epic
Command: npx skills add https://github.com/hirokimry/vibecorp --skill release-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual coordination work required to release a completed epic, so a team can verify child issue completion, create the release pull request, and keep the parent issue in sync without touching application code.

Core Features & Use Cases

  • Epic readiness validation: Checks that the parent issue is a real epic and that every child issue is closed before release starts.
  • Release PR creation: Builds a main-targeted pull request from the matching feature/epic branch and generates release notes from child issue titles.
  • Issue tracking updates: Posts or appends release status back to the parent epic issue so the release state remains visible in GitHub.
  • Guardrailed workflow: Prevents duplicate release PRs, avoids auto-merge, and stops safely when the preset, branch, or issue state is not ready.

Quick Start

Ask the assistant to release the specified parent epic issue and create the corresponding GitHub release pull request only after confirming that all child issues are closed.

Frequently Asked Questions about release-epic

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

FAQPage Schema
How do I automatically create a release pull request for a GitHub epic when all child issues are closed?

To create a release pull request for a GitHub epic, the workflow validates that all child issues are closed, generates release notes from their titles, and opens a main-targeted PR from the feature/epic branch. It also updates the parent epic issue status.

What is the best way to generate release notes from child issue titles for an epic branch?

Generating release notes from child issue titles is handled automatically during the release pull request creation process. The workflow extracts the titles from closed child issues and compiles them directly into the PR description for the parent epic.

How does duplicate pull request detection work for epic release workflows?

Duplicate pull request detection prevents the creation of multiple release PRs for the same epic branch. The workflow checks for existing open pull requests targeting main from the feature/epic branch and safely stops if a release PR is already present.

Do I need GitHub CLI access to automate epic release pull requests?

Yes, GitHub CLI access is required to automate epic release pull requests. The workflow relies on the GitHub CLI to verify child issue statuses, create the release PR, generate notes, and post status updates back to the parent issue without modifying application code.

Can I auto-merge the release pull request after creating it from an epic branch?

No, auto-merge is intentionally avoided when creating a release pull request from an epic branch. The workflow stops safely after PR creation and parent issue updates, ensuring a human reviews the compiled release notes before merging into main.

Why does my epic release workflow stop before creating a pull request?

An epic release workflow stops before creating a pull request if the parent issue is not a real epic, if any child issues are still open, or if the required preset and feature/epic branch configurations are not properly set up.