Codex Uni20 Doc Sync for Async API Behavior
Update Uni20 developer documentation when public behavior changes, with particular attention to ordering, lifetime, cancellation, and consistent API terminology.
中文Install in Codex
Codex with a Uni20 checkout and access to AGENTS.md, source, and docs.
- Copy the entire pinned `.codex/skills/uni20-doc-sync/` directory to `.agents/skills/uni20-doc-sync/` in the target checkout.
- Open Codex in that checkout and invoke `$uni20-doc-sync` with the example task and desired output.
Example task
Invoke `$uni20-doc-sync` after an async cancellation change in a scratch branch. Ask it to validate one example against the branch implementation and document call ordering and resource lifetime.What to check
The cancellation explanation and example match current code. The report identifies changed pages and any remaining gaps.
Original SKILL.md on GitHub · Updated
Frequently asked question
What details matter in an async example?
Explain ordering, lifetime, and cancellation where each affects correct use by callers.