skills.rest
tegnike
tegnikeCOMMUNITY
Explore all skills by this author →
Website𝕏@tegnikeGitHub

develop-main-release

Automates merging develop into main and publishing tagged GitHub releases for aituber-kit.

1.1k|206|Updated Oct 14, 2023
Search Tags:#release#CodeRabbit#Automation#version bump#gitHub#git tag#Pull request
One-click install
npx skills add https://github.com/tegnike/aituber-kit --skill develop-main-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: develop-main-release
Source: https://github.com/tegnike/aituber-kit/tree/main/.agents/skills/develop-main-release
Command: npx skills add https://github.com/tegnike/aituber-kit --skill develop-main-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing a new minor version of aituber-kit involves many error-prone manual steps: bumping the app version, verifying PR checks and CodeRabbit review threads, merging, tagging, and drafting release notes. This Skill codifies that entire workflow into a safe, repeatable procedure.

Core Features & Use Cases

  • Version Bump Management: Updates the single source of truth in src/constants/appVersion.json and verifies the footer and startup logo reflect it.
  • Safe Merge Gating: Confirms all PR checks pass, mergeStateStatus is CLEAN, and no unresolved CodeRabbit review threads remain before merging.
  • Release Publishing: Creates a lightweight tag, generates release notes from the PR body with CodeRabbit auto-generated content stripped out, and publishes the GitHub Release.
  • Use Case: When a develop => main PR is ready, invoke this Skill to bump the version, merge the PR, tag vX.Y.0, and publish a clean GitHub Release with Discord-ready announcement text.

Quick Start

Merge the develop to main PR and release the next minor version of aituber-kit following the release skill procedure.

Frequently Asked Questions about develop-main-release

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

FAQPage Schema
How do I release a new minor version of aituber-kit?▼

Bump the version in src/constants/appVersion.json on develop, verify PR checks and CodeRabbit review threads are resolved, merge the develop-to-main PR, create a lightweight tag vX.Y.0, and publish a GitHub Release with cleaned notes.

How do I check CodeRabbit review threads before merging a PR?▼

Use the GitHub GraphQL API reviewThreads field to confirm no threads have isResolved false and isOutdated false. Flat review bodies alone are not sufficient to judge CodeRabbit status.

Does this release process use annotated or lightweight git tags?▼

The process uses lightweight tags created with git tag vX.Y.0 pointing at the main merge commit. Existing tags are never overwritten without explicit instruction.

How are GitHub Release notes generated from the PR body?▼

The develop-to-main PR body is copied, then everything after the CodeRabbit auto-generated comment marker is removed. CodeRabbit summaries and bot-derived wording are excluded or rewritten as concrete changes.

What happens if the release tag already exists?▼

The procedure stops if git ls-remote shows the target tag already exists on origin. It never overwrites an existing tag without explicit instruction.

Related Skills

Explore More Software Engineering Skills→
lachlanchenlachlanchen
1

prepare-pr

Rebase a GitHub pull request onto main, apply review fixes, run tests, and push.

Community
Advanced
openclawopenclaw
388.4k

release-openclaw-announcement

Draft Discord release announcements from changelog, tag, and validation evidence.

Official
Intermediate
mappa-aimappa-ai
1

handle-coderabbit

Triage and address CodeRabbit review comments on GitHub pull requests.

Official
Advanced
pythoninthegrassespythoninthegrasses
1

changelog-automation

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

Official
Advanced