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

develop-main-pr

Creates and updates release pull requests from develop to main on GitHub.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually writing release pull request bodies for the develop-to-main merge is repetitive and error-prone, especially when maintaining a consistent Japanese release-note format and excluding bot-generated content like CodeRabbit blocks.

Core Features & Use Cases

  • Standardized Release PRs: Generates PR bodies in the established Japanese release-note format with sections for new features, improvements, bug fixes, tests, and documentation.
  • Create or Update Logic: Detects an existing open develop-to-main PR and updates its body instead of creating a duplicate.
  • CodeRabbit Exclusion: Strips auto-generated CodeRabbit comment blocks so they do not leak into release notes.
  • Use Case: Before a release, run this Skill to inspect the diff between origin/main and origin/develop, then produce a clean "Develop => main" PR ready for review.

Quick Start

Create a release pull request from develop to main for aituber-kit following the usual Japanese release note format.

Frequently Asked Questions about develop-main-pr

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

FAQPage Schema
How do I create a release PR from develop to main with gh CLI?▼

Use gh pr create with --base main --head develop and a body file containing the release notes. This Skill automates that flow by inspecting the diff between origin/main and origin/develop and generating the body in the standard format.

How do I update an existing pull request body with GitHub CLI?▼

Run gh pr edit <pr-number> --body-file with the new body content. The Skill first checks for an open develop-to-main PR with gh pr list and updates it instead of creating a duplicate.

How do I exclude CodeRabbit auto-generated comments from a PR body?▼

Remove everything after the marker "<!-- This is an auto-generated comment: release notes by coderabbit.ai -->" when editing the PR body. This prevents bot-generated text from leaking into release notes.

Does this Skill merge the PR or create GitHub releases?▼

No. It only creates or updates the pull request body. Merging, tagging, version footer updates, and GitHub Release publishing are handled by the separate develop-main-release skill.

What tools are required to run a develop-to-main release PR workflow?▼

You need git for fetching and diffing branches and the GitHub CLI (gh) authenticated to the repository for listing, creating, and editing pull requests.

Related Skills

Explore More Software Engineering Skills→
OnClickListener2048OnClickListener2048

finishing-a-development-branch

Guide Git branch completion with merge, PR, or cleanup options after tests pass.

Community
Advanced
intrusive-memoryintrusive-memory
5

ship-swift-library

Automate Swift library releases by merging PRs, bumping versions, and publishing GitHub releases.

Official
Advanced
o3-ozonoo3-ozono

ship

Automate PR finalization and squash merges after CI and review validation.

Community
Advanced
nvimcraftnvimcraft

git-release

Generate release version recommendations and changelog drafts from Git history.

Community
Advanced