release

Automate GitHub PR release workflows with policy reviews and post-merge cleanup.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/jbaruch/coding-policy --skill release-jbaruch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/jbaruch/coding-policy/tree/main/skills/release
Command: npx skills add https://github.com/jbaruch/coding-policy --skill release-jbaruch

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Shipping code via GitHub PRs often requires manual coordination across readiness checks, reviews, and post-merge cleanup. This Skill provides an end-to-end, repeatable workflow that coordinates PR creation, automated policy reviews, and branch management to reduce cycle time and error-prone handoffs.

Core Features & Use Cases

  • End-to-end PR lifecycle: from feature-branch creation to PR merge with policy reviews and automated checks.
  • Readiness gating and verification: ensures tests pass, linting succeeds, and formatting adheres to project standards before merging.
  • Post-merge verification and cleanup: cleans up branches, validates version bumps, and triggers publish workflows after merge.

Quick Start

Push a feature branch and run the release script to automatically open a PR, trigger policy reviews, and merge when approved.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate end-to-end GitHub PR releases with policy reviews?

You can automate end-to-end GitHub PR releases by running a script that opens PRs, triggers automated policy reviews, ensures tests pass, and merges when approved. This coordinates readiness checks, reviews, and post-merge cleanup into a repeatable workflow.

What is the best way to automate post-merge cleanup and version validation for GitHub PRs?

Automating post-merge cleanup involves cleaning up branches, validating version bumps, and triggering publish workflows after merge. This reduces manual coordination and error-prone handoffs once your GitHub PR is merged.

Do I need gh and jq installed to automate PR readiness checks and linting?

Yes, you need both gh and jq installed. These dependencies are required to execute the scripts that automate readiness gating, verify tests and linting pass, and format PRs to adhere to project standards before merging.

Can I use automated policy reviews for feature-branch PRs in my software team workflow?

Yes, automated policy reviews are explicitly designed for software teams using GitHub for feature-branch PRs. The workflow integrates policy reviews with gh-aw to coordinate PR creation and automated feedback loops.

How does readiness gating work for GitHub PRs before merging?

Readiness gating ensures tests pass, linting succeeds, and formatting adheres to project standards before merging. It acts as an automated verification step within the GitHub PR lifecycle to prevent error-prone handoffs.

Why does my GitHub PR release workflow require manual coordination across checks and cleanup?

Manual coordination happens because readiness checks, policy reviews, and post-merge cleanup are often disconnected. Automating the end-to-end release workflow coordinates these steps, reducing cycle time and eliminating manual handoffs.