Awesome-omni-skill cgr-docs-governance
Use this skill when updating project documentation after backend/frontend operational changes, incidents, workflow behavior changes, or new runbooks.
install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/documentation/cgr-docs-governance" ~/.claude/skills/diegosouzapw-awesome-omni-skill-cgr-docs-governance && rm -rf "$T"
manifest:
skills/documentation/cgr-docs-governance/SKILL.mdsource content
CGR Docs Governance
Goal
Keep documentation aligned with code and production behavior.
Scope
- root README
- docs/README
- docs/03_guia_desarrollo.md
- docs/04_operacion_y_mantenimiento.md
- docs/99_briefing_agente_experto.md
Workflow
- Identify behavior changes from code diff.
- Validate claims against production evidence if operational.
- Update docs with concrete commands and interpretation notes.
- Ensure no stale numbers/dates remain without timestamp.
Rules
- Prefer explicit dates in status notes.
- Include runbooks, not only descriptions.
- Document known incidents with cause and mitigation.
References
references/update-checklist.md