Rule Auditor Skill

Audits governance rule implementation across codebase and interfaces.

Updated May 13, 2026
One-click install
npx skills add https://github.com/cliffthelin/AXiomEngine --skill rule-auditor-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Rule Auditor Skill
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/archon/.claude/skills/rule-auditor
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill rule-auditor-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you verify that governance rules (by Rule ID or logic) are actually implemented in your codebase, then packages audit-ready metadata for traceability.

Core Features & Use Cases

  • Atomic rule alignment scrutiny: Searches the codebase for a specific Rule ID or associated logic to confirm whether the rule is reflected in implementation.
  • Metadata generation for discovery: Produces a compact summary and keyword tags derived from the rule text for indexing and review.
  • Interface audit coverage: Checks whether the rule is exposed via CLI, TUI, or GUI entry points (and reports when it is missing).
  • Hierarchical JSON export: Writes results into a structured JSON form suitable for downstream tooling and reporting.

Quick Start

Run the rule auditor workflow for a given Rule ID and rule text to generate an interface-validated, audit-friendly JSON record.

Frequently Asked Questions about Rule Auditor Skill

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

FAQPage Schema
How do I verify if a governance policy rule is actually implemented in my codebase?

To verify policy compliance, audit governance rules by searching the codebase for a specific Rule ID or associated logic to confirm whether the rule is reflected in the implementation. This detects drift between policy and code.

What is codebase alignment for governance metadata and when do I need it?

Codebase alignment for governance metadata matches policy rules to source code implementations and generates structured JSON records. You need it for rule-by-rule compliance verification and audit-ready traceability reporting.

How do I check if a compliance rule is exposed across CLI, TUI, and GUI interfaces?

To check interface exposure for a compliance rule, run an interface audit that detects CLI, TUI, or GUI entry points and marks missing surfaces. This ensures full interface coverage for governance rules.

Can I export rule auditing results into a structured JSON format for downstream tooling?

Yes, you can export rule auditing results into a hierarchical JSON format suitable for downstream tooling. The output includes summaries capped at 500 characters and tag arrays for indexing.

What is the best way to generate audit-ready metadata tags from a policy rule text?

The best way to generate audit-ready metadata from rule text is to extract keyword tags as a JSON array and create a compact summary. This packages the rule for governance metadata indexing and review.

Does the rule auditing process require any specific external dependencies or environments?

No external dependencies are required for the rule auditing process. It operates independently using scripts to search the codebase and generate governance metadata without prerequisite packages.