cgr-docs-governance — community cgr-docs-governance, community, ide skills

v1.0.0

About this Skill

Perfect for Code Maintenance Agents needing advanced documentation governance and version control capabilities. Use this skill when updating project documentation after backend/frontend operational changes, incidents, workflow behavior changes, or new runbooks.

fermaf fermaf
[0]
[0]
Updated: 2/28/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
18
Canonical Locale
en
Detected Body Locale
en

Perfect for Code Maintenance Agents needing advanced documentation governance and version control capabilities. Use this skill when updating project documentation after backend/frontend operational changes, incidents, workflow behavior changes, or new runbooks.

Core Value

Empowers agents to maintain accurate and up-to-date documentation by analyzing code diffs, validating claims against production evidence, and updating documentation with concrete commands and interpretation notes, utilizing Markdown files such as README and guia_desarrollo.md.

Ideal Agent Persona

Perfect for Code Maintenance Agents needing advanced documentation governance and version control capabilities.

Capabilities Granted for cgr-docs-governance

Automating documentation updates after code changes
Validating production behavior against documented claims
Ensuring documentation consistency across multiple files, including 03_guia_desarrollo.md and 04_operacion_y_mantenimiento.md

! Prerequisites & Limits

  • Requires access to code repository and documentation files
  • Limited to Markdown-based documentation
  • Needs production environment evidence for validation

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is cgr-docs-governance?

Perfect for Code Maintenance Agents needing advanced documentation governance and version control capabilities. Use this skill when updating project documentation after backend/frontend operational changes, incidents, workflow behavior changes, or new runbooks.

How do I install cgr-docs-governance?

Run the command: npx killer-skills add fermaf/cgr/cgr-docs-governance. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for cgr-docs-governance?

Key use cases include: Automating documentation updates after code changes, Validating production behavior against documented claims, Ensuring documentation consistency across multiple files, including 03_guia_desarrollo.md and 04_operacion_y_mantenimiento.md.

Which IDEs are compatible with cgr-docs-governance?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for cgr-docs-governance?

Requires access to code repository and documentation files. Limited to Markdown-based documentation. Needs production environment evidence for validation.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add fermaf/cgr/cgr-docs-governance. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use cgr-docs-governance immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

cgr-docs-governance

Install cgr-docs-governance, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

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

Looking for an alternative to cgr-docs-governance or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer