plugin-doctor

Auditing Codex repositories involves scanning .agents/skills, plugins, and related manifests to enforce frontmatter presence, validate marketplace and plugin manifests, and detect drift between source skills and packaged artifacts.

You detect drift by running a repository audit that compares source SKILLs under .agents/skills against packaged artifacts under plugins, flagging metadata inconsistencies and manifest reference mismatches automatically.

You validate Codex manifests by auditing .codex-plugin/plugin.json and marketplace.json to ensure content consistency and verify that external references match the actual repository structure.

Yes, you can identify legacy Claude residue such as CLAUDE.md files during a repository audit, which flags these artifacts to ensure safe deployment and structural consistency for Codex plugins.

Yes, the Codex skill audit enforces frontmatter presence of name and description fields across repo-local skills under .agents/skills, ensuring metadata completeness and preventing incomplete skill definitions.

The audit is limited to validating repository-local structures under .agents/skills, plugins, and related manifests, focusing on structural consistency and legacy residue detection rather than runtime behavior or functional testing.