production-readiness-audit

Audit a Claude Code plugin for consistency, coherence, completeness, and invariant conformance.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill production-readiness-audit-docktermj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: production-readiness-audit
Source: https://github.com/docktermj/senzing-bootcamp-claude-plugin-development/tree/main/.claude/skills/production-readiness-audit
Command: npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill production-readiness-audit-docktermj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Whole-plugin properties like consistency, coherence, and completeness cannot be verified by a test suite, so a plugin can pass every test while its files contradict each other or its ruleset silently drifts from what it ships. This Skill performs the final static audit of the Senzing Bootcamp plugin before a live dry-run, checking the plugin against its INVARIANTS.md ruleset in both directions. ## Core Features & Use Cases - Bidirectional invariant audit: Verifies every invariant is honored at every site it binds (forward), and that every durable rule the plugin states is registered as an invariant (reverse). - Lead-generating scans: Ships a stdlib-only Python tool (conformance.py) with views for hard rules, per-rule citations, rules added since the last audit, enumerations, duplication, and file size. - Structured defect handling: Records findings as GitHub issues or ledger entries, fixes defect classes rather than instances, and requires negative-controlled regression tests. - Use Case: Before shipping a new version of the plugin, a maintainer runs this audit to catch contradictions between sibling skill files, stale enumerations in invariants, and hard rules that shipped with no governing invariant. ## Quick Start Ask the assistant to run the production-readiness audit on the Senzing Bootcamp plugin and report findings by severity.

Frequently Asked Questions about production-readiness-audit

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

FAQPage Schema
How do I audit a Claude Code plugin for production readiness?▼

Run this Skill after confirming the test suite is green. It reads recent audit ledger entries, runs the conformance.py lead generators, then sweeps invariants forward and reverse before reporting findings by severity.

What is a bidirectional invariant audit?▼

The forward direction checks that every invariant in INVARIANTS.md is honored at all sites it binds. The reverse direction checks that every durable rule the plugin states is registered as an invariant, catching guarantees that shipped with nothing binding future work to them.

Can a test suite replace this kind of consistency audit?▼

No. Tests assert specific facts about specific places and cannot notice that an unchecked location disagrees. Every prior audit ran against a fully green suite and still found real defects, such as rules applied to only some of the sites they bind.

Does the conformance.py script require external dependencies?▼

No. The script is stdlib-only, read-only, and always exits 0. Its output is a set of leads to read and classify manually, not verdicts, since a regex cannot distinguish a deliberately restated rule from one that drifted.

What are the limitations of a static plugin audit?▼

Static analysis only confirms the plugin agrees with itself, not with the world. Conversational invariants governing live model behavior cannot be verified by reading and are routed to a dry-run phase instead.