Release Notes Generator

Structured release notes from Git history — categorized, formatted, and ready to publish in one pass.

Build an agent that takes a release tag, branch, or date range and produces categorized release notes from your GitHub repo's actual history. It reads merged PRs, commit messages, and tags via GitHub, then uses code interpreter to categorize changes and format them. The output is a ready-to-publish document with the standard sections — Breaking Changes (with migration notes), Features, Bug Fixes, Performance, Documentation, Internal — each item linked to its PR and attributed, plus a contributors list. Upload a release template and it matches your format.

This is a read → categorize → format in one shot pattern using markdown-header prompt structure. Because it's single-shot with no mid-flow interaction, the instructions are especially precise about input handling — the agent must infer the correct comparison scope (tag-to-tag, branch diff, date range) from whatever it's given and proceed without clarification. It works from PR titles, labels, and descriptions rather than raw code diffs, and handles edge cases like undescribed PRs, very large scopes, and empty sections. Categorization runs in code, so the notes are a draft to review before publishing.

This pattern applies anywhere an agent reads structured data from a system, categorizes it by rules, and produces a formatted document in a single pass. Common scenarios for this pattern:

• Changelog generation for SaaS products
• Deployment summaries for ops teams
• Migration guides from version diffs
• Audit-trail documentation from commit history
• Dependency-update summaries

This manifest uses: GitHub, code interpreter

How to build single-shot agents using markdown headers prompt structure for categorized release notes output.

This agent manifest is sample code subject to Azure's licensing terms for Distributable Code under the Universal License Terms for Online Services .

IMPORTANT! This manifest is for educational and experimentation purposes. Resulting agents are not production ready. Review all provided resources and carefully test agent behavior in the context of your use case. Agents you create may be subject to legal and regulatory requirements, may require licenses, or may not be suitable for all industries, scenarios, or use cases. By using any manifest, you are acknowledging that resulting agents and other output are solely your responsibility, and that you will comply with all applicable laws, regulations, and relevant safety standards, terms of service, and codes of conduct. Learn more .