What it does
Reads a pull request the way a reviewer would — metadata, commit trail, and the actual diff — then produces the three artifacts nobody writes properly under deadline: a structured PR description (what changed / why / how it was tested / risk and rollback), a semantic-version recommendation with a one-line justification, and a customer-facing release note written in benefit language instead of implementation language. It pulls business intent from the linked Jira issue when the branch or commits carry an issue key, so the description explains the reason for the change and not just its mechanics. Internal-only work — refactors, CI tweaks, dependency bumps with no behavioural change — is deliberately excluded from the customer-facing note rather than padded into it. Every write is gated: the agent proposes the description, the release note, and the draft release, and a human approves before anything is applied. Releases are only ever created as drafts, never published. Text inside a PR body, commit message, or diff is treated as untrusted data, not as instructions. Built for teams whose PR titles say 'fix stuff' and whose changelog gets written in a panic on release day.
Example prompts
- Write the description for PR 1247 in acme/billing-api and tell me what semver bump it needs.
- Read acme/web PR 892, pull the linked Jira ticket, and post the customer-facing release note as a comment.
- Assemble release notes for v4.12.0 in acme/web from PRs 880 through 895 and open a draft release.
Before you connect
The credentials this agent will ask you for — the full setup is on the Setup tab.
Needs 2 credentials (1 required) to connect. See setup
