What problem does it solve? Writing release notes for an AL/Business Central app means manually reviewing every merged PR since the last release, classifying changes, and drafting consistent markdown — a slow, error-prone process that often produces vague entries like "Updated logic". ## Core Features & Use Cases - Automated PR Analysis: The PowerShell script Get-ReleaseAnalysis.ps1 extracts all merged PRs between releases via git log and GitHub CLI, producing a structured JSONL file with summaries, file categories, and breaking-change indicators. - Per-PR Classification: Each PR is classified as feature, improvement, bugfix, breaking, technical, or excluded using a defined protocol, with a Deep Dive fallback for vague entries. - Structured Markdown Output: Renders canonical release notes with emoji-marked sections (New Features, Improvements, Bug Fixes, Breaking Changes, Technical Summary) written to .output/releases/RELEASE-NOTES-<VERSION>.md. - Use Case: After merging a dozen PRs for version 27.7.0 of a Business Central app, run the skill to produce complete, self-contained release notes with named pages, actions, and migration steps — no PR links required. ## Quick Start Ask the agent to generate release notes for the current version of the app, and it will run the analysis script, classify each merged PR, and write the final markdown file.
