# Document Release

> Post-ship documentation sync for Codex. Use when shipped changes should be reflected in README, architecture docs, contributor docs, or release notes.

- Skill: `mphaxise/document-release` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mphaxise/document-release`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mphaxise/document-release/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: mphaxise (https://skillmd.com/u/mphaxise)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mphaxise/document-release

---


# Document Release

Use this skill after implementation or release work when the documentation should be brought back into sync with reality.

This port is adapted from `garrytan/gstack` at commit `4d2c8d94d00cc4f4f3d4c26316a4f939ceedc045`.

## Workflow

1. Read the relevant diff or shipped change summary.
2. Identify which docs are now stale:
   - `README.md`
   - architecture docs
   - contributor docs
   - runbooks
   - changelog or release notes
3. Update only the docs actually affected by the change.
4. If a durable release artifact is useful, save it via the `reports` pattern.

## Guardrails

- Do not invent docs the repo does not use.
- Prefer correcting stale statements over rewriting everything.
- Keep documentation aligned with the actual shipped behavior, not the aspirational future.