How do I install the Chr Governance skill?

Run npx skillmds@latest add chenghaoran14237-lgtm/chr-governance in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Chr Governance safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Chr Governance?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Chr Governance free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Chr Governance?

chenghaoran14237-lgtm (@chenghaoran14237-lgtm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Chr Governance by chenghaoran14237-lgtm

Name: Chr Governance
Rating: 4.2 (5 reviews)
Author: chenghaoran14237-lgtm

Chr Governance

Govern project documentation and AI-facing instruction files with CHR. Use when the user says chr:check, chr:sync, chr:gc, "use chr for document governance", "用 chr 进行文档治理", or asks to initialize, check, synchronize, or clean AGENTS.md, DOCS_POLICY.md, .chr.toml, governed docs, OpenSpec docs, stale docs, superseded docs, archived docs, waivers, or git-aware documentation impact.

File contents

CHR Governance

CHR is a lightweight project-fact governance layer. It keeps Codex anchored to current, trusted documents and the local git state. It does not replace tests, OpenSpec validation, code review, debugging, release workflows, or architecture audits.

Core Rules

Treat only status: active governed documents as current implementation authority.
Treat draft, deprecated, superseded, and archived documents as non-current unless explicitly needed as history.
Treat README.md as a human portal by default, not implementation authority.
Treat AGENTS.md as an agent entry map, not a knowledge base.
Anchor checks to HEAD plus staged, unstaged, and untracked local changes.
Say "affected document was touched" or "may need review"; do not claim that a document is semantically synchronized unless the content was actually reviewed.

Deterministic Script

Prefer the bundled script for checks:

python3 <skill-dir>/scripts/chr.py check --root <repo>

Python 3.11+ is required. The script reads .chr.toml, .chr/waivers.toml, governed document frontmatter, relative links, and local git status.

Legacy wrappers are kept for compatibility:

python3 <skill-dir>/scripts/check_docs_lifecycle.py --root <repo>
python3 <skill-dir>/scripts/docs_inventory.py --root <repo>

User Workflows

General request: "use chr for document governance"

Run scripts/chr.py check --root <repo>.
If the project is not_initialized, run scripts/chr.py init --root <repo> unless the user requested check-only behavior.
Fix deterministic governance issues you can safely fix: missing metadata, broken governed links, stale AGENTS.md links, superseded/archived references, and missing minimal governance entry files.
Use the git-aware impact report to identify affected active docs. Update only docs that are clearly affected by the local changes.
If an impact is real but intentionally does not require a doc update, add a time-limited waiver in .chr/waivers.toml.
If impact semantics are unclear, leave a warning in the final answer instead of inventing architecture claims.
Run scripts/chr.py check --root <repo> again and report the version anchor, changed governance files, and remaining warnings.

`chr:check`

Run the checker and report health. Do not edit files.

`chr:sync`

After code/spec/product changes, run the checker, update affected active docs, adjust lifecycle metadata on touched docs, add waivers only when justified, and run the checker again.

`chr:gc`

Run the checker and clean lifecycle issues the user expects you to clean now. CHR is not a daemon; cleanup is user-triggered or stage-triggered. Do not rely on time passing to perform cleanup automatically.

References

Load only what is needed:

references/commands.md: command behavior and final-report expectations.
references/project-config.md: .chr.toml and .chr/waivers.toml schema.
references/frontmatter.md: governance metadata and status semantics.
references/agents-md-rules.md: AGENTS.md constraints.
references/policy-template.md: recommended DOCS_POLICY.md.
references/openspec-integration.md: CHR and OpenSpec boundaries.
references/gc-checklist.md: user-triggered cleanup checklist.

---name: chr-governancedescription: Govern project documentation and AI-facing instruction files with CHR. Use when the user says chr:check, chr:sync, chr:gc, "use chr for document governance", "用 chr 进行文档治理", or asks to initialize, check, synchronize, or clean AGENTS.md, DOCS_POLICY.md, .chr.toml, governed docs, OpenSpec docs, stale docs, superseded docs, archived docs, waivers, or git-aware documentation impact.---# CHR GovernanceCHR is a lightweight project-fact governance layer. It keeps Codex anchored tocurrent, trusted documents and the local git state. It does not replace tests,OpenSpec validation, code review, debugging, release workflows, or architectureaudits.## Core Rules- Treat only `status: active` governed documents as current implementation authority.- Treat `draft`, `deprecated`, `superseded`, and `archived` documents as non-current unless explicitly needed as history.- Treat `README.md` as a human portal by default, not implementation authority.- Treat `AGENTS.md` as an agent entry map, not a knowledge base.- Anchor checks to `HEAD` plus staged, unstaged, and untracked local changes.- Say "affected document was touched" or "may need review"; do not claim that a document is semantically synchronized unless the content was actually reviewed.## Deterministic ScriptPrefer the bundled script for checks:```bashpython3 <skill-dir>/scripts/chr.py check --root <repo>```Python 3.11+ is required. The script reads `.chr.toml`, `.chr/waivers.toml`,governed document frontmatter, relative links, and local git status.Legacy wrappers are kept for compatibility:```bashpython3 <skill-dir>/scripts/check_docs_lifecycle.py --root <repo>python3 <skill-dir>/scripts/docs_inventory.py --root <repo>```## User Workflows### General request: "use chr for document governance"1. Run `scripts/chr.py check --root <repo>`.2. If the project is `not_initialized`, run `scripts/chr.py init --root <repo>` unless the user requested check-only behavior.3. Fix deterministic governance issues you can safely fix: missing metadata, broken governed links, stale `AGENTS.md` links, superseded/archived references, and missing minimal governance entry files.4. Use the git-aware impact report to identify affected active docs. Update only docs that are clearly affected by the local changes.5. If an impact is real but intentionally does not require a doc update, add a time-limited waiver in `.chr/waivers.toml`.6. If impact semantics are unclear, leave a warning in the final answer instead of inventing architecture claims.7. Run `scripts/chr.py check --root <repo>` again and report the version anchor, changed governance files, and remaining warnings.### `chr:check`Run the checker and report health. Do not edit files.### `chr:sync`After code/spec/product changes, run the checker, update affected active docs,adjust lifecycle metadata on touched docs, add waivers only when justified, andrun the checker again.### `chr:gc`Run the checker and clean lifecycle issues the user expects you to clean now.CHR is not a daemon; cleanup is user-triggered or stage-triggered. Do not rely ontime passing to perform cleanup automatically.## ReferencesLoad only what is needed:- `references/commands.md`: command behavior and final-report expectations.- `references/project-config.md`: `.chr.toml` and `.chr/waivers.toml` schema.- `references/frontmatter.md`: governance metadata and status semantics.- `references/agents-md-rules.md`: `AGENTS.md` constraints.- `references/policy-template.md`: recommended `DOCS_POLICY.md`.- `references/openspec-integration.md`: CHR and OpenSpec boundaries.- `references/gc-checklist.md`: user-triggered cleanup checklist.

Frequently asked questions