check-downstream-consumers

Name: check-downstream-consumers
Availability: InStock
Author: Flutter

Validates breaking changes in dart_skills_lint package dependencies against downstream consumer repositories.

2.8k|166|Updated Feb 25, 2026

Search Tags:#testing #linting #migration #flutter #breaking-changes #dart

Ready to run

npx skills add https://github.com/flutter/agent-plugins --skill check-downstream-consumers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-downstream-consumers
Source: https://github.com/flutter/agent-plugins/tree/main/tool/dart_skills_lint/.agents/skills/check-downstream-consumers
Command: npx skills add https://github.com/flutter/agent-plugins --skill check-downstream-consumers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of ensuring that breaking changes in the dart_skills_lint package do not inadvertently break downstream consumer repositories, providing a safe, diagnostic environment for verifying migrations.

Core Features & Use Cases

Diagnostic Verification: Safely tests how downstream consumers handle API changes without committing changes to their repositories.
Migration Testing: Validates that changelog migration instructions are accurate and effective by applying them to real-world consumer codebases.
Use Case: When introducing a breaking change to the linter, use this skill to verify that repositories like flutter/flutter or flutter/devtools can successfully migrate to the new API surface without build failures.

Quick Start

Use the check-downstream-consumers skill to evaluate the impact of the current branch on all known downstream repositories.

Frequently Asked Questions about check-downstream-consumers

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

FAQPage Schema

How do I test breaking changes in Dart packages against downstream repos?▼

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.

What is the best way to verify Flutter API migration accuracy before committing?▼

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.

Can I check if downstream consumers like flutter/devtools handle linter updates safely?▼

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.

How does validating Dart linter changes work without modifying the consumer repository?▼

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.

When do I need to run downstream consumer validation for a Dart linter package?▼

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.

Are there limitations to testing breaking changes across local repositories?▼

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.