auto-bmad-compat-check

Diffs published bmad-method and TEA npm packages against auto-bmad's parsed contracts to assess release compatibility.

30|8|Updated May 27, 2026
One-click install
npx skills add https://github.com/stefanoginella/auto-bmad --skill auto-bmad-compat-check-stefanoginella
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-bmad-compat-check
Source: https://github.com/stefanoginella/auto-bmad/tree/main/.claude/skills/auto-bmad-compat-check
Command: npx skills add https://github.com/stefanoginella/auto-bmad --skill auto-bmad-compat-check-stefanoginella

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Maintainers of the auto-bmad repo need to know whether new releases of the two npm packages it delegates into — bmad-method and bmad-method-test-architecture-enterprise (TEA) — break the contracts auto-bmad parses, the review-layer asset it ships, or the skills it delegates to, without manually re-reviewing already-checked versions. ## Core Features & Use Cases - Incremental per-package diffing: Downloads published npm tarballs and diffs only what is new since the last-checked stable and prerelease versions, anchored from the README compat blockquote. - Contract-aware classification: Tags every changed file as critical, high, low, shim, or info based on whether it owns a contract auto-bmad parses (sprint-status.yaml grammar, HALT protocol, review_layers schema) or is a delegated bmad-testarch-* skill. - Release-note cross-check and marker updates: Guides cross-referencing GitHub release notes and post-stable commits via gitHead, then offers to advance the README badge, compat blockquote, and CHANGELOG markers. - Use Case: After BMAD ships v6.12.0, run the check to see only the delta since your last verified version, confirm no parsed contract moved, and advance the compatibility markers in one pass. ## Quick Start Run /auto-bmad-compat-check from the root of the auto-bmad repo to check both BMAD packages for compatible new releases.

Frequently Asked Questions about auto-bmad-compat-check

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

FAQPage Schema
How do I check if a new bmad-method release breaks auto-bmad?

Run /auto-bmad-compat-check from the auto-bmad repo root. It downloads the published npm tarballs, diffs them incrementally from your last-checked versions, and classifies each changed file by whether it touches a contract auto-bmad parses or a skill it delegates to.

How does the compatibility check avoid re-reviewing old changes?

It stores the last-checked stable and prerelease versions in the README compat blockquote and anchors each diff at the highest version already reviewed. Each run surfaces only what is genuinely new since the last check, per package.

Does the check cover the TEA test-architecture package?

Yes, bmad-method-test-architecture-enterprise is checked in the same run with its own independent version line. The bmad-testarch-* skills are classified as high relevance, and the headline verdict is the worst of the two package verdicts.

What happens if the network or gh CLI is unavailable?

Without network access the helper script exits with a clear error and the check stops. If gh is unauthenticated, the skill falls back to the tarball-only verdict, since the release-note cross-check sharpens judgement but is not a gate.

When should I not update the README compatibility markers?

Do not advance markers when a critical or high change actually breaks a parsed contract, and never raise the floor version during a routine check. The two packages' markers advance independently, so only update the clauses you re-verified clean.