Release notes describe unshipped features
You generate user-facing release notes with an AI from a batch of merged PRs. One line reads: 'Added dark mode support across the dashboard.' Looking at the PRs, dark mode was only added to the settings page, and one PR that was reverted before release still shows up as a shipped feature. How do you verify AI-generated release notes describe what actually shipped, not just what the PRs talked about?
Implement
net_shipped_titles(pr_events: list[str]) → list[str]Examples
in
[["merge|101|Add dark mode to the settings page","merge|102|Speed up dashboard search","revert|102|"]]out["Add dark mode to the settings page"]in
[["comment|103|Dark mode across the dashboard is planned","merge|104|Fix CSV export encoding"]]out["Fix CSV export encoding"]in
[["merge|105|Add retry to webhook sender","revert|105|","merge|105|Add retry to webhook sender (fixed)"]]out["Add retry to webhook sender (fixed)"]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 12 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.