Codex Project Documentation Updates for Released UI Defaults
Keep operational docs aligned with shipped route, page and option behavior and specify exact paths and defaults.
中文Install in Codex
Open RegentClaw in Codex with the released UI change, route and current instructions. The sample uses a fictional list screen.
- Review `.agents/skills/docs-update/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/docs-update/` in your project and save the reviewed file as `.agents/skills/docs-update/SKILL.md`.
- Start Codex from that project's root, then type `$docs-update` and select the matching skill.
Example task
Update the docs for this sample display page.
{"page":"saved filters","route":"/saved-filters","defaultView":"recent","includeArchived":false,"archivedOptionOptIn":true}What to check
Add `/saved-filters`. Document `defaultView=recent` and `includeArchived=false`, and note that archived entries are opt-in.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should an unreleased option be documented as current?
Describe behavior that is confirmed shipped in current operational docs. Track planned options separately.