What problem does it solve? Manually converting raw assertions like expect(count($array))->toBe(5) into idiomatic Pest matchers across a large test suite is tedious and error-prone, and running Rector without the right configuration silently rewrites application code instead of tests. ## Core Features & Use Cases - Automated matcher conversion: Applies the 60-rule PestSetList::CODING_STYLE set to rewrite assertions into matchers like toHaveCount and toHaveKey, scoped strictly to tests/. - Generated-config trap prevention: Forces writing rector.php before any Rector invocation, since Rector auto-generates an app-wide config on non-TTY shells that performs zero Pest refactoring. - Dry-run gated workflow: Requires a green --no-tia baseline, a reviewed --dry-run diff, Pint formatting, and a post-run regression check before committing. - Use Case: After upgrading a Laravel project to Pest 5, run this skill to modernize thousands of existing Pest tests into chained matcher syntax with a verifiable, test-only blast radius. ## Quick Start Ask the agent to run the laravel-pest-rector workflow to refactor the tests directory into Pest matchers with a dry-run preview first.