lc:test-coverage

To find untested Laravel controllers and actions, this skill scans your source files and matches them against existing tests. It evaluates models, controllers, actions, and services to generate a prioritized report of untested components based on complexity and business logic.

The best way to prioritize testing efforts for a Laravel refactor is using automated coverage mapping. This skill estimates testing priority by analyzing class complexity, database interactions, and business logic density to highlight high-risk regression areas.

Yes, you can check Laravel test coverage without executing tests by using static analysis. This skill determines coverage status by analyzing naming conventions and class references to match source files directly against existing test suites.

Yes, this test coverage analysis supports identifying untested models and services. It automatically scans these application classes alongside controllers and actions to map them against your test files and provide actionable testing recommendations.

To generate a prioritized report of untested business logic in Laravel, run the analysis on your entire project. The skill evaluates your application classes and outputs a summary highlighting untested components based on their estimated risk and complexity.