check-downstream-consumers

To test breaking changes in Dart packages against downstream repos, this skill temporarily updates dependency references and runs verification tests across local repositories to ensure API compatibility.

The best way to verify Flutter API migration accuracy is through transient diagnostic analysis, which safely applies changelog migration instructions to real-world consumer codebases without committing changes.

Yes, you can check if downstream consumers like flutter/devtools handle linter updates safely by evaluating the impact of your current branch on all known downstream repositories in a diagnostic environment.

Validating Dart linter changes works without modifying the consumer repository by operating transiently, temporarily updating dependency references to run verification tests and ensuring compatibility before discarding changes.

You need to run downstream consumer validation for a Dart linter package when introducing a breaking change, ensuring repositories like flutter/flutter can successfully migrate to the new API surface without build failures.

A limitation of testing breaking changes across local repositories is that the skill only operates on identified local repositories, meaning it cannot validate API compatibility for external consumers outside the known ecosystem.