governance-status

Runs deterministic repository checks to report governance health and adapter drift status.

5|9|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ajenchen/design-system --skill governance-status-ajenchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governance-status
Source: https://github.com/ajenchen/design-system/tree/main/.agents/skills/governance-status
Command: npx skills add https://github.com/ajenchen/design-system --skill governance-status-ajenchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams maintaining generated governance surfaces across multiple AI providers need a fast, provider-neutral way to verify that adapters, snapshots, and contracts are current and consistent without manually running each check. ## Core Features & Use Cases - Deterministic Health Checks: Runs four repository-owned commands covering governance doctor, codex adapter generation, fork governance builds, and provider surface tests. - Structured Status Output: Returns a compact PASS/FAIL/BLOCKED table per check plus one overall state: HEALTHY, DRIFTED, INVALID, or BLOCKED. - Read-Only Operation: Never regenerates, repairs, installs, or modifies anything unless the user separately requests a fix. - Use Case: Before merging a change to the design-system canonical skills, ask for a governance status check to confirm no adapter drift or provider parity issues exist. ## Quick Start Ask the assistant to run a governance status check on this repository and report whether it is healthy, drifted, invalid, or blocked.

Frequently Asked Questions about governance-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check governance status in a repository?

Run the four deterministic checks: npm run governance:doctor, the codex adapter check, the fork governance build check, and the provider surface test. Each check is marked PASS, FAIL, or BLOCKED, followed by one overall state.

What does DRIFTED mean in a governance health check?

DRIFTED means a generated projection or snapshot differs from its authoritative source, such as an adapter view that no longer matches the canonical skill definition. It signals that regeneration is needed but does not happen automatically.

Does the governance status check modify or repair files?

No. The checks are strictly read-only and never regenerate, repair, install, publish, or modify anything. Fixes only occur when the user separately requests them.

Why does a governance check report BLOCKED instead of FAIL?

BLOCKED indicates required tooling or files are unavailable, such as missing Node.js, npm scripts, or test files. FAIL means the check ran but its contract, surface, or inventory validation did not pass.

Can hook availability alone confirm a repository is healthy?

No. Hook availability is not authoritative for governance health. Only the deterministic checks and CI results determine whether the repository is HEALTHY, DRIFTED, INVALID, or BLOCKED.