skills.rest
FgForrest
FgForrestOFFICIAL
Explore all skills by this author →
Website𝕏@forrestiGitHub

release-pr

Create or update GitHub PRs from dev to master with auto-generated release notes.

70|7|Updated Feb 22, 2023
Search Tags:#automation#git#github#release#pr#release-notes#pgp
One-click install
npx skills add https://github.com/FgForrest/evitaDB --skill release-pr-fgforrest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-pr
Source: https://github.com/FgForrest/evitaDB/tree/main/.claude/skills/release-pr
Command: npx skills add https://github.com/FgForrest/evitaDB --skill release-pr-fgforrest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release management is cumbersome and error-prone when creating and updating release PRs and compiling release notes; this skill automates PR creation, updates, and notes generation to accelerate releases.

Core Features & Use Cases

  • Auto-generate release notes from milestones and commits.
  • Create or update a GitHub PR from dev to master with proper metadata and release notes.
  • Validate PGP signatures as part of the release workflow to maintain a secure supply chain.

Quick Start

Trigger the release-pr workflow to create or update a release PR from dev to master with auto-generated release notes.

Frequently Asked Questions about release-pr

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

FAQPage Schema
How do I auto-generate release notes for a GitHub PR from dev to master?▼

You can auto-generate release notes for a GitHub PR by triggering a workflow that assembles notes from milestones and commits, then creates or updates a PR from dev to master with proper metadata.

Can I verify PGP signatures as part of my GitHub release workflow?▼

Yes, PGP signature verification is integrated into the release workflow to maintain a secure supply chain when creating or updating release PRs.

How does version extraction work for release PR automation?▼

Version extraction works by reading the pom.xml file and detecting the base version against origin/master to determine the correct release version for PR management.

Do I need the gh CLI to manage release PRs from dev to master?▼

Yes, the gh CLI is required for PR management, including creating, updating, and validating release PRs from dev to master with auto-generated notes.

What's the best way to automate release management and reduce errors in PR creation?▼

Automating release management via a workflow that creates, updates, and compiles release notes from milestones and commits reduces errors and accelerates releases.

Related Skills

Explore More Software Engineering Skills→
TrainLCDTrainLCD
71

sync-dev-from-master

Automates creation of synchronization pull requests from master to dev branches using gh CLI and git.

Official
Advanced
drvossdrvoss
42

release

Automates version tagging, changelog generation, GitHub Releases, and artifact publishing to registries.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

quality-run-linters

Run Mojo format, markdownlint, and pre-commit hooks for code quality checks.

Official
Intermediate
Tonybleything76Tonybleything76

Changelog Generator

Generate changelog entries from Git commit history using Conventional Commits.

Community
Advanced