audit-plugin

Audits Claude Code plugins via multi-stage independent reviews and convergence loops.

15|6|Updated May 7, 2026
One-click install
npx skills add https://github.com/MinhThang1009/dotclaude --skill audit-plugin-minhthang1009
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-plugin
Source: https://github.com/MinhThang1009/dotclaude/tree/main/plugins/audit-plugin/skills/audit-plugin
Command: npx skills add https://github.com/MinhThang1009/dotclaude --skill audit-plugin-minhthang1009

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditing Claude Code plugins for content quality is often manual, error-prone, and fragmented. This skill formalizes a repeatable, multi-stage review process that ensures independent validation, user-controlled fixes, and convergence to a clean, compliant plugin baseline.

Core Features & Use Cases

  • Independent 7-criteria Stage 1 review with Stage 5 fresh rounds.
  • Validators and audit ledger management.
  • User approval gates for fixes.
  • Optional benchmark Stage 6 for executable workflows with consent.

Quick Start

Supply the target plugin path to audit-plugin to start the multi-stage review.

Frequently Asked Questions about audit-plugin

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

FAQPage Schema
How do I audit a Claude Code plugin for content quality and governance?

To audit a Claude Code plugin for content quality, supply the target plugin path to initiate a multi-stage review process that applies strict validation criteria, user approval gates, and convergence loops until all issues are resolved.

What is a multi-stage convergence loop in plugin code review?

A multi-stage convergence loop in plugin code review is a process where independent validators assess a plugin across seven stages, repeating fresh review rounds until all identified quality and governance issues are fully resolved.

How do I validate Claude Code plugin compliance with structured evidence requirements?

You validate Claude Code plugin compliance by running a multi-stage audit that enforces structured evidence requirements, manages validation artifacts, and generates a report with findings, status, and remediation guidance.

Can I review plugin quality without manual intervention during the audit stages?

You cannot review plugin quality completely without manual intervention, because the audit process enforces user approval gates for fixes across stages 1 through 7 and requires explicit consent for optional benchmark execution.

What is the best way to ensure independent validation of a Claude Code plugin?

The best way to ensure independent validation of a Claude Code plugin is to apply a formalized 7-criteria review process with dedicated validators, an audit ledger, and fresh review rounds to converge on a clean, compliant baseline.

Why does my Claude Code plugin audit require user approval for fixes?

Your Claude Code plugin audit requires user approval for fixes to maintain user-controlled remediation, ensuring that all validation steps, artifact management changes, and proposer prompts meet governance standards before convergence.