What problem does it solve? Writing release pull requests that merge develop into main is tedious: you must review every merged PR, translate technical changes into language non-developers can read, and remember to check for risky changes like new environment variables or breaking API modifications. This Skill automates that entire workflow. ## Core Features & Use Cases - Automated change collection: Builds the change list from git log origin/main..origin/develop and enriches it with PR titles and bodies via gh pr view. - Audience-split release notes: Generates a description with separate User-facing and Internal changes sections, grouped by category, so product managers, designers, and customer success teams can read what matters to them. - Release caution checks: Verifies new environment keys, external-app impact, DB migrations, and feature flags against the actual diff, and reports each result even when it is None. - Use Case: Before a weekly production deploy, ask for a release PR and receive a ready-to-review develop-to-main PR with complete release notes and a caution checklist, or have the existing open release PR updated in place. ## Quick Start Create a release PR from develop to main with release notes and caution checks for this repository.
