compatibility-audit

Detect cross-target bundle drift and validate ycc compatibility for Claude, Cursor, Codex, and opencode.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/yandy-r/claude-plugins --skill compatibility-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compatibility-audit
Source: https://github.com/yandy-r/claude-plugins/tree/main/.cursor-plugin/skills/compatibility-audit
Command: npx skills add https://github.com/yandy-r/claude-plugins --skill compatibility-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) components.

What problem does it solve?

This skill audits the health of every generated compatibility target for the ycc plugin — Claude, Cursor, Codex, and opencode — and produces a structured, per-target triage report. It detects bundle drift, validates generated bundles, and surfaces install-assumption issues and feature gaps without modifying any code or bumping versions.

Core Features & Use Cases

  • Drift detection: compare the source ycc/ tree against each target bundle to identify missing or out-of-date content.
  • Per-target validation: run target-specific validators and surface issues without modifying any source files.
  • Install-assumptions and feature-gap surfacing: verify install paths, permissions, and capability parity across targets; produce both human and JSON outputs for release readiness.
  • Pre-release readiness: use before /bundle-release to validate before releasing.

Quick Start

Run the compatibility-audit from repository root to generate a per-target report without altering source trees.

Frequently Asked Questions about compatibility-audit

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

FAQPage Schema
How do I detect bundle drift between source code and generated targets before a release?

Cross-target compatibility audits validate generated bundles for Claude, Cursor, Codex, and opencode by comparing the source tree against each target to surface install-assumption issues and feature gaps without modifying code.

Can I validate install assumptions for plugin bundles without bumping versions?

Cross-target compatibility audits validate generated bundles for Claude, Cursor, Codex, and opencode by comparing the source tree against each target to surface install-assumption issues and feature gaps without modifying code.

How do I generate a JSON compatibility report for Claude, Cursor, Codex, and opencode targets?

Cross-target compatibility audits validate generated bundles for Claude, Cursor, Codex, and opencode by comparing the source tree against each target to surface install-assumption issues and feature gaps without modifying code.

Does the compatibility audit require Python 3 to run drift detection scripts?

Cross-target compatibility audits validate generated bundles for Claude, Cursor, Codex, and opencode by comparing the source tree against each target to surface install-assumption issues and feature gaps without modifying code.

What is the best way to check cross-target feature parity without altering the source tree?

Cross-target compatibility audits validate generated bundles for Claude, Cursor, Codex, and opencode by comparing the source tree against each target to surface install-assumption issues and feature gaps without modifying code.

What limitations exist when auditing generated bundles for release readiness?

Cross-target compatibility audits validate generated bundles for Claude, Cursor, Codex, and opencode by comparing the source tree against each target to surface install-assumption issues and feature gaps without modifying code.