wit-breaking-change-check
Classify WIT interface changes as breaking or non-breaking against frozen version markers. Use this skill when the user wants to check WIT breaking changes, review a WIT diff, verify whether a WIT change is breaking, or run a WIT compat check. Trigger on: 'check WIT breaking changes', 'review WIT diff', 'is this WIT change breaking', 'WIT compat check'.
pinned to #ae30776updated 2 weeks ago
Ask your AI client: “install skills/wit-breaking-change-check”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/wit-breaking-change-checkmetahub onboarded this repo on the author's behalf.
If you own github.com/zeroclaw-labs/zeroclaw on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
32,224
Last commit
2 weeks ago
Latest release
published
- #agent
- #agentic
- #ai
- #infra
- #ml
- #openclaw
- #os
- #zeroclaw
About this skill
Pulled from SKILL.md at publish time.
Classifies every modification in the current WIT diff against the breaking-change taxonomy and reports a verdict for each finding.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.ae30776· 2 weeks ago
Safety
11LICENSE file at repo rootwarn
No LICENSE / LICENCE / COPYING / UNLICENSE file (.md/.txt/.rst variants) and no SPDX-License-Identifier header found in common source files
Pick an SPDX license and add a LICENSE file at the repo root, or put an `SPDX-License-Identifier:` comment at the top of your main source file.
No sensitive files in the repo
scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found
Release history
1- releasecurrentae30776warn2 weeks ago
Contents
Classifies every modification in the current WIT diff against the breaking-change taxonomy and reports a verdict for each finding.
When to Use
- Before merging any branch that touches
wit/ - When reviewing a PR that modifies WIT interface definitions
- To verify a WIT change is safe before publishing a plugin-compatible release
Procedure
- Run
git diff origin/master -- wit/to obtain the current diff. - For each
wit/vN/directory in the diff, check whetherwit/vN/.frozenexists. If absent, report the version as experimental and skip it. - For each frozen version with changes, classify every modification against the breaking-change taxonomy in
wit/VERSIONING.md:- Breaking: removing/renaming any type, function, record field, or variant case; changing a function signature; changing a field type; reordering record fields; adding a required (non-optional) field to an existing record; adding a non-capability-gated required function to an existing interface.
- Non-breaking: new
flagsbits, new capability-gated functions, new record/variant/enum types, new interfaces, new worlds,@since/@unstableannotation additions.
- Report each finding with a verdict:
- ✅ Non-breaking — with a brief reason citing the taxonomy
- ❌ Breaking — with a brief reason citing the taxonomy
- ⚠️ Uncertain — with the ambiguity explained
- If any breaking change is found, summarize the required migration path for plugin authors.
Notes
The .frozen marker is a human-readable convention: its presence signals to reviewers and this skill that the version is stable and requires the breaking-change check before merge. Experimental (unfrozen) versions are skipped without a verdict.
Reviews
No reviews yet. Be the first.
Related
Gpt Researcher
An autonomous agent that conducts deep research on any data using any LLM providers
Planning With Files
Claude Code skill implementing Manus-style persistent markdown planning — the workflow pattern behind the $2B acquisition.
Verification Before Completion
Evidence before assertions, always
mh install skills/wit-breaking-change-check