self-audit

Audit Rune workflow definitions, hooks, and agent prompts for inconsistencies and drift.

6|3|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/vinhnxv/rune --skill self-audit-vinhnxv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-audit
Source: https://github.com/vinhnxv/rune/tree/main/plugins/rune/skills/self-audit
Command: npx skills add https://github.com/vinhnxv/rune --skill self-audit-vinhnxv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Rune's self-audit provides a formal, structured health check of the plugin-driven workflow system. It identifies drift, contradictions, and gaps across workflow definitions, hooks, and agent prompts, enabling timely fixes.

Core Features & Use Cases

  • Static governance: validate metadata completeness, phase sequencing, hook registrations, and cross-field consistency.
  • Grounding verification: ensure cited files and lines exist and evidence matches quotes.
  • Delta analysis: compare current findings against previous MEMORY entries to surface new, persistent, or resolved issues and track trends.

Quick Start

Run the Rune self-audit to generate the SELF-AUDIT-REPORT.md.

Frequently Asked Questions about self-audit

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

FAQPage Schema
How do I check workflow definitions for inconsistencies and drift?

To check workflow definitions for inconsistencies, you run a formal self-audit to identify and quantify drift, contradictions, and gaps across hooks and agent prompts, generating a structured report with per-dimension scores.

What is static governance for agent prompts and hook integrity?

Static governance is the validation of metadata completeness, phase sequencing, hook registrations, and cross-field consistency to ensure agent prompts and workflow definitions maintain structural health.

How do I verify cited files and evidence lines exist during a workflow audit?

You verify cited files and evidence lines through grounding checks, which ensure that referenced files and lines physically exist and that the provided evidence matches the original quotes.

How do I track persistent or resolved issues across multiple workflow runs?

You track persistent or resolved issues across runs using cross-run delta analysis, which compares current findings against previous MEMORY entries to surface new issues and monitor resolution trends.

Does the self-audit workflow health check require any external dependencies?

No, the self-audit workflow health check requires no external dependencies, allowing you to directly validate taxonomy, hook integrity, and runtime governance within your existing environment.