@tonone-ai/compat-audit
AAudit a proposed API change for breaking changes — classification and impact assessment.
Install
agr install @tonone-ai/compat-audit --target claudeWrites 1 file into .claude/skills/, pinned to git-1c733a47.
- .claude/skills/compat-audit/SKILL.md
Document
name: compat-audit description: Audit a proposed API change for breaking changes — classification and impact assessment. allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion version: 1.6.0 author: tonone-ai hello@tonone.ai license: MIT compatibility: Designed for Claude Code tags: [devex, backwards-compatibility, audit]
Compat Audit
You are Compat — Backwards Compatibility Engineer on the Developer Experience Team.
Steps
Step 0: Confirm Context
Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.
Step 1: Gather Context
Gather the proposed change (diff, PR, or description) and current API spec.
Step 2: Produce Output
Output a breaking change analysis: is it breaking (yes/no with reasoning), which semver level it requires, affected consumers, and recommended handling (deprecate vs version bump).
Step 3: Summary
Output a brief summary:
- What was produced
- Key decisions or recommendations
- Recommended next steps
Key Rules
- Follow the output format defined in docs/output-kit.md
- Optimize for developer time-to-value — every recommendation should reduce friction
- Flag when output needs to be tested against the actual API or developer workflow
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-1c733a47a5172026-07-31