/postman:syncchanges: sync what changed

This is the one you'll run most. After you write code and commit, it syncs only what changed, and you never have to think about git refs to use it.

Usage

/postman:syncchanges [--last N] [--since commit|date]

For free-form instructions (add error responses, headers, a rewritten description, …), use /postman:prompt instead.

Default behavior

With no flags, it syncs everything changed since lastUpdate.commit, the marker written by your last sync. You never name a git ref yourself.

Flag	Effect
(none)	Everything changed since the last sync.
--last 3	The last 3 commits. No need to remember HEAD~3 syntax.
--since 2026-06-01	Everything since a date.
--since a1b2c3d	Everything since a specific commit.

First run with no marker

If there's no lastUpdate.commit yet, the command errors gently and suggests /postman:syncall for the initial full sync.

How each change is handled

Change type	Behavior
New route	Full create.
Modified route	Only the changed structural fields are updated; human-owned scripts and examples are preserved.
Deleted route	Noted in the sync notes, not auto-removed or deprecated yet — deletion handling is still manual. Remove the stale request from the collection by hand.

Why it's cheap

syncchanges parses only the files that changed since the last marker, not the whole project, and reads just the collection's basic structure rather than mirroring it locally. That's what keeps token usage low enough to run after every change instead of saving it up.

Example

<edit routes/payments.py, commit>
/postman:syncchanges

Collection: Acme Backend
Plan: 1 new · 1 modified

[MODIFY] POST /payments   → (root)   ✓ verified (routes/payments.py:12)
[NEW] GET /payments/{id}   → (root)   ✓ verified (routes/payments.py:24)

Write to Postman? Re-run with confirm=true to apply.

Once the write result is shown, the command ends; no further analysis or follow-on commentary.

Free-form instructions

syncchanges itself is plain and deterministic. For anything free-form (add error responses, headers, a rewritten description), use /postman:prompt "<text>" — Claude drives this same changed-routes sync under the hood and applies the changes through the same diff-then-confirm gate. See the Prompt & skill layer.