Assess package and runtime compatibility
SkillDev toolsGuides your agent through checking that a WordPress package stays compatible across different package and WordPress versions.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Assess package and runtime compatibility skill
About this capability
Use when changing or reviewing a published package across independently updated package and WordPress versions, including API, dependency, entrypoint, registration, allowlist, opt-in, and compatibility changes.
What this skill tells your AI
The instructions your AI receives, as published by wordpress/gutenberg in .agents/skills/package-runtime-compatibility/SKILL.md and read by ahel’s review.
- Read Testing published packages across WordPress versions.
- Identify what the consumer bundles, what WordPress supplies, and which versions can run together. Include every supported entrypoint.
- Run the guide's existing-consumer check and, when WordPress supplies a dependency, its four version combinations. Use the built package. Check published types, dependency extraction, behaviour, and any state that separate package copies must share.
- Before removing compatibility code, find the maintained bundles that still use it. Mark every required combination as
pass,fail, orunverified. Do not remove the code while a required combination is unverified. - When adding coverage, follow the testing skill and reproduce the unsupported combination before adding its fallback.
- Report the evidence, release order, required support change, and any unverified combination.
Signals
- GitHub stars
- 12k
- Forks
- 5k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
package-runtime-compatibility- Source
- github.com/wordpress/gutenberg