---
name: post-retro
description: Use when deciding whether an already-published Bike Riding Robot post needs a substantive revision or a minor fix, and drafting that change.
---

Handles revisions to posts that are already live. Doesn't touch unpublished drafts — that's the rest of the pipeline, starting at [post-ideate](../post-ideate/SKILL.md).

## Steps

1. Read the published post and whatever prompted the revisit: new information, a correction, reader feedback, or something in the world the post described that's since changed.
2. Classify the change. A typo, broken link, or formatting fix needs no version bump. A change to a claim, number, or argument is substantive — bump the post's `version` frontmatter field (add it at `1` if it isn't present yet, since this predates most posts having one) and note what changed and why.
3. For a substantive change, run a scoped [post-factcheck](../post-factcheck/SKILL.md)-style verification and [post-voice-edit](../post-voice-edit/SKILL.md)-style pass on just the changed section — not the whole post.
4. Produce a one-line changelog note for the user to keep track of (this site has no public changelog surface, so it isn't published anywhere automatically).