Compare approved changes with code and prepare notes for review
Use this Agent instantly or customize it - no programming needed
Your checklist's move into the writing step starts a draft for that release.
Your checklist names the approved changes and target code reference. It also identifies your release manager.
Your published tags and dates show which public release precedes the target.
Your code comparison shows commits and changed files between the prior release and target.
Your template sets the headings and tone for the notes your manager reviews.
Your issue tracker signals the writing step and holds the approved changes and target reference.
Your code repository shows the previous public release and the code changes through the target.
Your release manager gets a needs-review page with source links. It contains supported notes or gaps to resolve.
Your release notes workspace keeps draft pages in a shared queue for your release manager's review.
Your release manager gets a needs-review page with source links. It contains supported notes or gaps to resolve.
Your release manager gets a needs-review page with source links. It contains supported notes or gaps to resolve.
This Agent waits for your release checklist to reach the writing step. It compares approved changes with code since the last published version. It places a formatted draft and review questions in your queue.
Customize this Agent to fit your needs using natural language.
Enter your email address and we will send you a secure link to continue.
Airtable shows the previous public release and the code changes through the target.
Airtable keeps draft pages in a shared queue for your release manager's review.
monday.com signals the writing step and holds the approved changes and target reference.
monday.com shows the previous public release and the code changes through the target.
monday.com keeps draft pages in a shared queue for your release manager's review.
Asana shows the previous public release and the code changes through the target.
Microsoft Office 365 signals the writing step and holds the approved changes and target reference.
GitHub shows the previous public release and the code changes through the target.
Podio keeps draft pages in a shared queue for your release manager's review.
Superhuman Docs keeps draft pages in a shared queue for your release manager's review.
Kintone shows the previous public release and the code changes through the target.
Kintone keeps draft pages in a shared queue for your release manager's review.
Draft Release Notes is made for businesses in these industries.
Draft product release notes from approved changes and code comparisons.
Show all Agents for the Software industryDraft patch notes for review from approved game changes and code.
Show all Agents for the Video Games industryDraft Release Notes is made for people in these roles.
Prepare release note drafts with source links and questions to resolve.
Show all Agents for the Release Manager roleDraft Release Notes is made for people in these departments.
Match approved changes to release code before drafting notes for review.
Show all Agents for the Release Management department5 steps, in order, on every run.
Connect the tools you already use, such as Airtable, monday.com or Asana.
8 toolsUse safe mode to approve every result before it goes out, or let the Agent run automatically.
Frequently asked questions about the Draft Release Notes:
Choose your checklist project and writing status. Add approved changes, a repository link, and a target tag or commit. Provide your note format, release manager, and review queue.
Your release manager gets a review page naming the missing details or comparison gap. They can confirm the baseline before finishing the notes.
Your release manager sees the mismatch as a review question. The draft leaves that change unconfirmed until they resolve it.
No. Your release manager reviews the draft in your shared queue before publication.
It stops and asks you. The Agent does not guess when it reaches a decision you have not approved.
Yes. Every run creates a plain-language log that you can review and export. Logs are kept for twelve months.
The Agent stops at the end of the billing month and its tool connections are removed. Your run logs remain available for twelve months.