DOWNLOADABLE CODEX SKILL · v1.0.0

Synchronize project documentation

Keep setup, command, configuration, and behavior documentation aligned with the repository.

THE WORKFLOW

What this skill helps you do

Keep setup, command, configuration, and behavior documentation aligned with the repository. It keeps the work tied to evidence and the project’s actual constraints.

When it fits

The user asks to update docs after code or configuration changes. Download the package, inspect its instructions, and adapt its review notes to the project.

Try it on a real task

EXAMPLE REQUEST

$aboutcodex-docs-sync Update the README and admin help after adding skill collections.

What to look for

Documentation that matches the current project behavior and verified commands.

Install the skill

Inspect the extracted package first. For a local project, place the skill folder here:

.agents/skills/aboutcodex-docs-sync/SKILL.md

Desktop app

Open the project and inspect the Skills sidebar to locate the skill by name. Follow the skill controls available in your current desktop application.

Terminal / CLI

Open the project in Codex CLI. Use /skills or $aboutcodex-docs-sync to select the skill explicitly.

IDE extension

Open the project in the Codex IDE extension. Use /skills or $aboutcodex-docs-sync to select the skill explicitly.

Verify discovery: locate the exact skill name before starting. If missing, check the folder, SKILL.md filename, and name/description frontmatter, then restart the client.

After selecting the skill, use this inspection request:

Read the aboutcodex-docs-sync skill. Explain its purpose, inputs, and boundaries. Do not edit files or run its workflow yet.

Documentation-based guidance, checked September 10, 2026. Client discovery was not independently tested here. OpenAI’s skill documentation. Troubleshoot installation

Inspect the files

  • aboutcodex-docs-sync/SKILL.md1 KB
  • aboutcodex-docs-sync/references/NOTES.md461 B
  • aboutcodex-docs-sync/LICENSE.txt1 KB
Read SKILL.md before downloading
---
name: "aboutcodex-docs-sync"
description: "Keep setup, command, configuration, and behavior documentation aligned with the repository. Use when the user asks to update docs after code or configuration changes."
---

# Synchronize project documentation

Keep setup, command, configuration, and behavior documentation aligned with the repository.

## Workflow

1. Identify the changed public behavior, configuration, command, or support boundary.
2. Find every authoritative documentation location and avoid duplicating guidance that should be linked.
3. Run or inspect commands before documenting their results and prerequisites.
4. Update examples, defaults, paths, and version references in the same change.
5. Check links and compare the final documentation with the actual interface or configuration.

Read `references/NOTES.md` before finalizing the work. Follow project instructions and the user's authorized scope. Use available evidence, label assumptions, and never report a check as passing unless it actually ran.

## Deliverable

Documentation that matches the current project behavior and verified commands. State material limitations and link to changed files or rendered evidence when available.

Limits and considerations

Cannot validate external services or private environments that are unavailable.

Review notes

Structure checked · 2026-09-10

Required frontmatter, folder layout, file inventory, validator run, and generated ZIP round-trip checked. Workflow behavior has not been independently evaluated.

Package checks confirm file structure. They do not establish that a skill works well on every task.

Version notes

1.0.0 — Initial instruction-only release with supporting review notes.

Report an issue with this pageGet the next practical briefing

View saved items
Updates and upgrade guidance
  1. Installation guidance clarified · package v1.0.0

    Added interface-specific guidance and a read-only inspection request. The downloadable package is unchanged.

    What to do: No re-download needed for this documentation update. Inspect the current version and compare your local changes before replacing a skill.

This log starts with the first recorded review; it is not a reconstruction of earlier revisions.