Maintain user-facing Markdown documentation in `ops/docs` using one commit as discovery input, while actively curating global docs information architecture. Organize docs into clear area-based folders, maintain navigable indexes, and keep content focused on current user-visible behavior only.
Instalación
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Maintain user-facing Markdown documentation in `ops/docs` using one commit as discovery input, while actively curating global docs information architecture. Organize docs into clear area-based folders, maintain navigable indexes, and keep content focused on current user-visible behavior only.
Commit Docs Updater
Keep ops/docs continuously accurate as a site guide and navigable information architecture. A commit is discovery input only, never part of docs narration.
Inputs
Optional commit reference (<commit>).
If no commit is provided, use HEAD.
Treat exactly one commit as scope. Do not expand to ranges unless explicitly requested.
Core Rules
Commit-guided, not commit-written:
Use commit diff only to identify what user-facing areas might need docs updates.
Never include commit hashes, commit subjects, PR/change-log framing, or "what changed in commit" sections in ops/docs.
User-facing only:
Document behavior users can observe in UI/UX, routing, messaging, states, and outcomes.
Ignore non-user-facing changes such as tests, snapshots, internal refactors, type-only cleanup, tooling, and internal file moves unless they cause user-visible behavior changes.
Information architecture is part of the job:
Reorganize ops/docs when structure is flat, fuzzy, or hard to navigate.
Use area-based folders, clear file names, and index pages that support browsing.
Move, rename, split, merge, or remove docs pages when needed for clarity.
Timeless docs language:
Describe current behavior, not development history.
Write pages so they stay valid without needing commit context.
Current-state only:
Keep docs reflecting the latest structure and behavior.
Do not keep legacy compatibility pages, shim pages, or old-path placeholders.
Scale rules:
Root ops/docs/README.md must stay concise (target <=20 task links in I am trying to...).
If an area exceeds 12 content pages, create subarea folders with their own README.md indexes.
If an area has a topic cluster above 8 pages, split that cluster into a subarea even if total area pages are below 12.
Ownership rules:
Each user-facing behavior has one canonical docs page.
Cross-area visibility is handled through links, not duplicate pages.
Scope discipline:
Use commit scope to detect impacted capabilities, then apply enough structural cleanup to keep the docs system coherent.
