github-release-pr

Automate GitHub release pull requests between development and production branches.

Updated Oct 15, 2021
One-click install
npx skills add https://github.com/toqoz/config --skill github-release-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-release-pr
Source: https://github.com/toqoz/config/tree/main/home/agents/skills/github-release-pr
Command: npx skills add https://github.com/toqoz/config --skill github-release-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, codex, and includes scripts (resource) components.

What problem does it solve?

This skill automates the repetitive and error-prone process of managing release pull requests, ensuring that CI checks are verified and code reviews are performed before merging.

Core Features & Use Cases

  • Automated PR Lifecycle: Automatically creates or updates release PRs between specified branches based on project conventions.
  • CI Integration: Monitors CI status and waits for successful completion before proceeding with reviews.
  • AI-Powered Review: Executes a Codex code review on the release diff and appends the findings directly to the PR description.
  • Use Case: Use this when you need to promote code from a development branch to production, ensuring that all changes are reviewed and validated by CI without manual intervention.

Quick Start

Ask the agent to open a release pull request from the develop branch to the main branch.

Frequently Asked Questions about github-release-pr

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

FAQPage Schema
How do I automate release pull requests from develop to main?

Automate release pull requests by using this skill to create and synchronize PRs between development and production branches. It resolves branch differences and manages GitHub pull request metadata automatically.

Can I monitor CI status and wait for checks before merging a GitHub release PR?

Yes, monitor CI status directly through this skill. It integrates CI status monitoring to wait for successful completion of checks before proceeding with automated reviews or merges.

Do I need GitHub CLI and Codex CLI to automate release workflows?

Yes, you need GitHub CLI and Codex CLI installed. These dependencies are required to execute git operations, manage pull request metadata, and perform the automated static code analysis.

What's the best way to keep release PRs synchronized between branches?

The best way to keep release PRs synchronized is to automate the creation and update of pull requests based on project conventions. This skill handles branch resolution and updates existing release PRs automatically.

Why does my automated release workflow require static code analysis?

Automated release workflows require static code analysis to ensure code changes are reviewed before merging. This skill performs a Codex code review on the release diff to catch issues without manual intervention.