How we handle GDPR data-subject requests on a deadline
Legal
The pull-request review agent we run on Kortix — it flags PRs stuck past a review SLA, gone stale, or sitting on unaddressed change requests, then nudges the author or reviewer in Slack with exactly what's blocking.
A PR that sits unreviewed for three days doesn't announce itself. It just sits, under a growing pile of newer PRs, until the author pings someone directly or gives up and context-switches to something else. Multiply that across a team and a review SLA becomes a suggestion nobody enforces, and "requested changes" becomes a state a PR can live in indefinitely.
We run a PR review nudge agent on Kortix that reads every open pull request across our repos once a day and posts a Slack nudge for anything stuck: past the review SLA, gone stale, or sitting on unaddressed change requests. It only reads GitHub; the single output is the Slack nudge. It never merges, closes, or approves anything.
A review SLA is easy to write down and hard to enforce. Nobody is watching the review queue full-time, so a PR opened Monday morning and still unreviewed Wednesday afternoon looks the same in the repo list as one opened five minutes ago — until someone happens to scroll far enough to notice. Stale PRs are worse: a branch with no commits, no comments, and no reviews in a week has usually just been forgotten, and it silently rots until a rebase conflict forces someone to deal with it. And "requested changes" is a state, not an alert — a reviewer asks for changes, the author sees it, life happens, and the PR sits there looking open while actually being blocked.
The common approaches don't close this loop. GitHub's own notifications are easy to mute and don't distinguish a PR that's five minutes old from one that's five days old. A weekly standup catches the loudest blockers, not the quiet ones. Manually skimming the PR list is thorough the first time and skipped the second.
On Kortix, a daily cron triggers an agent. It spawns a fresh session with
read-only access to GitHub through the gh CLI, pulls every open PR across our
repos, and classifies each one against three rules: awaiting review past the
SLA, stale with no activity in N days, or carrying requested changes the author
hasn't addressed. For each PR that trips a rule, it posts a Slack nudge to the
person who owns the next move — the requested reviewer if it's overdue for
review, the author if it's stale or has unaddressed feedback — with a one-line
summary of what's actually blocking it.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the pr-review-sla skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a daily PR review nudge agent in this workspace.
Create the agent agents/pr-review-nudge.md. Its job is to find stuck pull requests on owner/repo and nudge the person who owns the next move. It reads GitHub with the gh CLI and the GH_TOKEN secret, and it may use the Slack connector.
Create the skill skills/pr-review-sla/SKILL.md with these rules:
Add a cron trigger daily-pr-review-sweep to kortix.yaml. It runs the pr-review-nudge agent every day at 08:00 with the prompt "Load the pr-review-sla skill and run one complete review sweep on owner/repo."
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.
Add a GitHub token with read access as the GH_TOKEN secret. It is injected at
runtime and scoped to this agent. Then open Connectors and connect Slack.
Credentials are brokered server-side and never enter the agent's machine.
Reads open PRs, review requests and activity, read-only.
Nudges the reviewer or author about what blocks each PR.
Merge the change request, then start a session with the pr-review-nudge agent and send this prompt. Replace owner/repo with your repository. Check who it nudges before you let the schedule take over.
Run one review sweep on owner/repo.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 08:00, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: daily-pr-review-sweep name: Daily PR review SLA sweep on: cron: "0 0 8 * * *" run: agent: pr-review-nudge prompt: Load the pr-review-sla skill and run one complete review sweep on owner/repo.Every GitHub call is a read. The agent never merges, closes or approves a PR, and never dismisses or resolves a review. The Slack summary is its only output. People decide what happens to each PR.
Each run ends with one summary in the channel. This is what a run looks like in the session:
Checked 17 open PRs and flagged 6. 3 wait on a review past the 24-hour SLA, 2 have had no activity for 3 days, and 1 has requested changes that the author has not addressed for 4 days.
Once it works, paste any of these into the same session.
Ignore draft PRs and PRs labeled wip, and say how many you skipped at the end of the summary.
Every Friday, post to #eng-reviews the median hours to first review for the PRs merged that week.
Also sweep owner/other-repo in the same run, and group the summary by repository.
The agent reads across every repo it's pointed at, so its access is scoped and strictly one-directional:
GH_TOKEN is encrypted in the Secrets Manager and
injected into the sandbox at runtime, scoped to the agents you grant them to.A review queue that used to require someone remembering to scroll through it now surfaces its own blockers every morning, in Slack, addressed to whoever owns the next move. The agent only reads and nudges; the team still decides what happens to every PR.