Write test
Use when adding or fixing a test in a Laravel project that uses Pest. Covers feature vs unit tests, factories, fixtures, failure-path coverage, and tenant-isolation assertions.From its SKILL.md
npx -y skills add yousefkadah/laravel-ai-kit --skill write-testAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 221 tokens by cl100k_base, as published. Nobody here has run it
Write a test
Setup
- Create with
php artisan make:test --pest {Name}(add--unitfor a unit test). Most tests are feature tests. - Use model factories and their states for data. Don't hand-build models.
Cover the right things
- The happy path and at least one failure path (validation error, timeout, unauthorized, bad input).
- Multi-tenant code: assert isolation — tenant A cannot see/modify tenant B's rows.
- Integrations & file formats: parse/serialize against real fixture files; assert on malformed input, not just clean input; for fixed-width/XML assert byte/schema-exact output.
Finish
- Run the narrowest useful command:
php artisan test --compact --filter={Name}. - Paste the command + output as evidence.
- Never delete/skip existing tests to make a change pass — fix the change or flag the conflict.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.