How we handle GDPR data-subject requests on a deadline
Legal
The release-notes agent we run on Kortix — connected to GitHub. On each release it reads the merged PRs since the last one, groups them, writes the notes, and opens a changelog PR.

Release notes are the first thing that gets skipped under a deadline. The information is all there in the merged PRs, but turning it into something a reader can follow — grouped by area, in plain language, with the noise dropped — is manual work that lands after the release is already out.
We run a release-notes agent on Kortix that does it from the PR history. On each release, the agent reads every PR merged since the last release, groups them by area, writes human-readable notes, and opens a PR to the changelog for review. This write-up covers how the setup works: the trigger, the session model, and the guardrails.
Writing release notes means reading back through everything that merged since the last release, deciding what a reader cares about, and phrasing it for someone who wasn't in the PRs. It's the kind of task that's easy to defer, so the changelog falls behind or gets a one-line summary that helps no one.
The common fixes are incomplete. An auto-generated list of PR titles is accurate but unreadable — internal wording, no grouping, every dependency bump included. Writing them by hand is better but slow, and it competes with actually shipping. Either way the notes arrive after the release, if they arrive at all.
On Kortix, each release triggers an agent. When a tag is pushed, the release spawns an isolated session (a cloud sandbox) with scoped access to the repository. The agent finds the previous release, reads every PR merged in between, groups them by area, writes notes in plain language, and opens a PR to the changelog. A human reviews and merges.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the changelog-sync skill and the hourly trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a release-notes agent in this workspace.
Create the agent agents/release-notes.md. Its job is to turn each new release of owner/repo into changelog notes and open a pull request against CHANGELOG.md. It may use the GitHub connector and the gh CLI with the GH_TOKEN secret.
Create the skill skills/changelog-sync/SKILL.md with these rules:
Add a cron trigger release-notes-check to kortix.yaml. It runs the release-notes agent every hour, on the hour with the prompt "Load the changelog-sync skill and check owner/repo for any release published since the last checkpoint."
Tell me which of these connectors are not connected yet. Tell me if the GH_TOKEN secret is missing.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect GitHub. Credentials are
brokered server-side and never enter the agent's machine. Then add a GitHub
token as the GH_TOKEN secret for the gh CLI. It is injected at runtime and
scoped to this agent.
Reads PRs merged since the last release and opens the changelog PR.
Merge the change request, then start a session with the release-notes agent and send this prompt. Replace owner/repo with your repository. Read the changelog PR it opens before you let the schedule take over.
Draft release notes for the latest release of owner/repo.
The change request added this trigger to kortix.yaml. From now on the agent
runs every hour, on the hour, each run on its own cloud computer. It reads its
checkpoint first, so it opens a PR only when a new release has shipped. To
change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: release-notes-check name: Release notes check on: cron: "0 0 * * * *" run: agent: release-notes prompt: Load the changelog-sync skill and check owner/repo for any release published since the last checkpoint.The agent writes only CHANGELOG.md, on its own branch, and opens a pull request. It never merges, tags, publishes or announces a release. A person edits the wording and merges.
Each new release gets one changelog PR. This is what a run looks like in the session:
Found 1 new release, v2.14.0. Read 21 merged PRs, dropped 9 as internal work or dependency bumps, and wrote 12 lines under Features, Fixes and Performance. Opened a PR against CHANGELOG.md for review.
Once it works, paste any of these into the same session.
End every changelog line with a link to the PR it came from.
Add a short release announcement to the changelog PR description, for a person to edit and post.
When a PR description is too thin to summarize, list it in the changelog PR description and mention its author so they can add one sentence.
The agent reads the repository and writes a draft, so the access is scoped and contained:
The changelog stops falling behind, and the notes that reach review are already grouped and readable instead of a raw list of PR titles. Reviewers edit wording rather than reconstructing what shipped from the git history.