cgr-docs-governance
Use this skill when updating project documentation after backend/frontend operational changes, incidents, workflow behavior changes, or new runbooks.
Best use case
cgr-docs-governance is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill when updating project documentation after backend/frontend operational changes, incidents, workflow behavior changes, or new runbooks.
Teams using cgr-docs-governance should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cgr-docs-governance/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cgr-docs-governance Compares
| Feature / Agent | cgr-docs-governance | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use this skill when updating project documentation after backend/frontend operational changes, incidents, workflow behavior changes, or new runbooks.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 1. Identify behavior changes from code diff. 2. Validate claims against production evidence if operational. 3. Update docs with concrete commands and interpretation notes. 4. 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`
Related Skills
google-docs-manager
Expert in Google Docs management. Use when creating, reading, updating, formatting, or managing Google Docs with markdown support, advanced formatting, tables with full manipulation, images with styling, lists, headers/footers, and table of contents.
genesis-tools:living-docs
Self-maintaining documentation system. Bootstraps, validates, refines, and optimizes codebase documentation. Creates minimal, token-efficient doc chunks. Use when creating, updating, or auditing project documentation.
generate-docstrings
Create docstrings for functions and classes. Use when documenting code APIs.
generate-agent-docs
Generates documentation and usage guides for agents, skills, prompts, and instructions. Works with GitHub Copilot, Claude Code, Codex, OpenCode, and other providers. Use when onboarding team members, creating README files for your customizations, or generating usage examples for existing agents.
feature-docs
[Documentation] Create or update business feature documentation in docs/business-features/{Module}/. Generates comprehensive 26-section docs with verified code evidence and AI companion files. Triggers on: feature docs, business feature documentation, module documentation, document feature, update feature docs, ai companion, ai context file, quick feature docs, feature readme, single file docs, verified documentation.
faf-docs
Access FAF documentation, guides, and resources. Answers questions about The Reading Order, IANA registration, Podium scoring, format specification, and best practices. Use when user asks "how does FAF work", "show me docs", "explain The Reading Order", or needs reference information.
explanation-docs
Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do
docsumo-automation
Automate Docsumo tasks via Rube MCP (Composio). Always search tools first for current schemas.
docs
Generates documentation files including NotebookLM YAML and slide content. Use when user mentions ドキュメント, document, YAML, NotebookLM, スライド, slide, プレゼン. Do NOT load for: 実装作業, コード修正, レビュー, デプロイ.
docs-verify
Validates documentation quality and freshness — checks for broken links, stale content, llms.txt sync, image issues, heading hierarchy, and badge URLs. Runs locally or in CI. Use to catch documentation decay before it reaches users.
docs-sync
Sync AILANG documentation website with codebase reality. Use after releases, when features are implemented, or when website accuracy is questioned. Checks design docs vs website, validates examples, updates feature status.
docs-plugin
Command: docs-plugin