skills.rest
hiddink-ai
hiddink-aiOFFICIAL
Explore all skills by this author →
GitHub

release-plan

Aggregate GitHub issues labeled verify-done into structured release plans with semantic versioning.

1|Updated May 21, 2026
Search Tags:#automation#workflow#planning#github#release#semver
One-click install
npx skills add https://github.com/hiddink-ai/hiddink-harness --skill release-plan-hiddink-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-plan
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/release-plan
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill release-plan-hiddink-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq.

What problem does it solve?

This skill eliminates the manual overhead of triaging, grouping, and scheduling GitHub issues for releases, ensuring that development plans are consistent, prioritized, and dependency-aware.

Core Features & Use Cases

  • Automated Issue Triage: Automatically collects and categorizes issues labeled verify-done based on priority and size.
  • Dependency-Aware Grouping: Groups issues into release units while respecting sequential dependencies and epic constraints.
  • Semantic Versioning: Calculates appropriate version bumps based on the content of the release, such as feature additions or breaking changes.

Quick Start

Execute the release-plan skill to generate a structured release plan document for all currently verified issues.

Frequently Asked Questions about release-plan

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

FAQPage Schema
How do I automate GitHub release planning from closed issues?▼

Automate GitHub release planning by collecting issues labeled verify-done, then grouping them into release units based on priority, size, and dependencies to generate a structured development plan.

How does semantic versioning work for grouped GitHub issues?▼

Semantic versioning for grouped issues calculates appropriate version bumps by analyzing release content, automatically recommending major, minor, or patch increments based on feature additions or breaking changes.

Can I group GitHub issues into releases while respecting dependencies?▼

Yes, dependency-aware grouping analyzes sequential dependencies and epic constraints to organize issues into release bins, ensuring no issues are dropped or deferred without explicit approval.

Do I need jq and gh to generate a structured release plan?▼

Yes, generating a structured release plan requires the gh CLI to aggregate GitHub issues and jq to process JSON data for dependency analysis and semantic versioning recommendations.

What is the best way to triage GitHub issues for an upcoming release?▼

The best way to triage issues for a release is to automatically collect and categorize items labeled verify-done, analyzing priority and size to produce organized, dependency-aware release bins.

How do I ensure no verified issues are dropped from a release plan?▼

To ensure no verified issues are dropped, the release planning process documents release scopes explicitly and prevents deferral of any issues without explicit approval during grouping.

Related Skills

Explore More Software Engineering Skills→
bitpantrybitpantry

create-issue

Create GitHub issues from text input with labels and context.

Community
Intermediate
pythoninthegrassespythoninthegrasses
1

changelog-automation

Generate changelogs and release notes from commits, PRs, and tags.

Official
Advanced
woohyun212woohyun212
21

devsecops-pipeline

Assess CI/CD pipeline security maturity and generate workflow files with security gates.

Community
Advanced
jacobcyjacobcy
6

vibe-roadmap

Assign GitHub issues to milestones and roadmap labels via gh.

Community
Intermediate