governance-health

Scans Git-owned governance telemetry to detect dead hooks, hot rules, and pending corrections.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Governance rules, hooks, and skills accumulate over time without visibility into which ones still fire, which are dead weight, and which user corrections should be codified. This Skill runs a monthly, read-only metric scan that turns raw telemetry into concrete retire, upgrade, and codify proposals. ## Core Features & Use Cases - Metric Harvesting: Reads opt-in telemetry logs (hook-fires, skill-invokes, user-corrections, metric-snapshots) through a canonical runtime resolver that rejects symlink and path-escape attempts. - Auto-Propose Engine: Flags hooks with zero fires in 6 months as retire candidates, rules firing over 50 times as Meta-Pattern upgrade candidates, and accumulated user corrections as codify candidates. - Health Report Generation: Produces a month-over-month trend report covering instruction line counts, hook fires, skill invokes, benchmark freshness, and infra-reference integrity. - Use Case: A repository maintainer asks whether any governance rules should be retired; the Skill scans six months of hook-fire telemetry, finds three dead hooks, and proposes them for the knowledge-prune queue without mutating any policy files. ## Quick Start Ask the assistant to run a governance health scan and report which hooks or rules should be retired or upgraded.

Frequently Asked Questions about governance-health

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

FAQPage Schema
How do I detect dead hooks in a repository governance setup?

Run a metric scan over hook-fires-per-hook telemetry covering a six-month window. Hooks with zero fires are flagged as retire candidates, but only after grepping the repository to confirm no remaining references exist.

How to decide which governance rules should be upgraded to meta-patterns?

Rules firing more than 50 times in six months indicate a recurring problem worth absorbing into a higher-level meta-pattern. The scan proposes specific upgrades with fire counts as evidence.

What is the difference between governance-health and knowledge-prune?

governance-health runs monthly and produces metric-driven proposals for retiring, upgrading, or codifying rules. knowledge-prune runs quarterly and performs deep structural refactoring of duplicates, contradictions, and dead content.

Does the governance health scan modify any policy files?

No, the scan is strictly read-only. It produces a report and routes confirmed findings to canonical owner skills for remediation, never mutating governance policy, memory files, or components itself.

What happens when telemetry logs are missing or not opted in?

The scan reports that instrumentation is not opted in or has not accumulated a one-to-two month baseline, then exits. Telemetry must reside in the real Git directory and is resolved through a canonical resolver that rejects symlink and escape attempts.