Skip to content

/postman:syncall: the whole codebase

Reads every route, controller, and model in the project and syncs all of it. Use it for first-time setup or after a big refactor. Always diffs first, same as every other write-capable command.

Usage

/postman:syncall [--into path]

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

Flags

Flag Effect
--into <path> Folder inside the collection every synced route lands in. If omitted, falls back to config.defaultInto, which defaults to the collection root. There's no automatic per-route folder inference; every route in the run goes to the same target.

When to use it

  • First run after init, to populate an empty or partial collection from scratch.
  • After a refactor, to reconcile the collection with sweeping code changes.

For everyday work, prefer /postman:syncchanges. It's much cheaper because it only looks at what changed instead of re-reading the whole project.

Example

/postman:syncall

Collection: Acme Backend
Plan: 21 new · 2 modified

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

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

Every route in a run lands in the same target: the collection root by default, or --into <path> if you gave one. Each line is labelled ✓ verified, ~ stale, or ⚠ CITATION DOES NOT MATCH CODE so you can see at a glance which requests are backed by real code before you write anything.

Routes removed from code

syncall doesn't currently mark a request deprecated just because the route behind it disappeared from the codebase — it only writes what it finds. Removing a stale request from the collection by hand is the workaround until this lands. Track it in ROADMAP.md.

Free-form instructions

syncall itself is plain and deterministic. For anything free-form (add error responses, headers, a rewritten description), use /postman:prompt "<text>" — Claude drives this same whole-codebase sync under the hood and applies the changes through the same diff-then-confirm gate. Because one instruction applies to every route in the run, keep it broad (e.g. "add the standard error set to everything"). See the Prompt & skill layer.