dart-migrate-to-checks-package

To migrate Dart tests from package:matcher to the checks API, you can use this Skill to automatically identify and rewrite legacy expect statements into the modern, fluent check-based syntax. It provides standardized conversion patterns for equality and type checking.

Refactoring Flutter unit tests to use package:checks is best handled by automating the transition from expect-based assertions to the fluent check-based API. This Skill facilitates the refactoring process while ensuring standardized syntax conversion for your test suite.

Yes, you can migrate asynchronous Stream and Future expectations in Dart to the checks API. This Skill provides clear, structured patterns specifically designed for migrating complex asynchronous operations from legacy matchers to the modern checks syntax.

Migrating to the checks package requires integration with Dart MCP tools for static analysis and test validation. This integration is necessary to ensure a zero-regression migration while refactoring assertions from package:matcher to the checks API.

Modernizing Dart test suites by moving away from package:matcher addresses technical debt and allows you to adopt the more readable and expressive checks API. This transition provides a structured path to improve your assertion syntax for both unit and widget tests.