// Use when user says "validate the task", "ensure everything is passing", "is everything ok?", "valide a entrega" (PT-BR), "garanta que tudo está funcionando" (PT-BR), "certifique-se de que está tudo ok" (PT-BR), or anything associated with the idea of validating a task.
Use ONLY when the user explicitly asks to open a PR — phrases like "open a PR", "abra um PR" (pt-BR), "abra um pull request" (pt-BR), "mande pra 3.x", "send the PR". Never trigger this skill on your own initiative, including under auto mode or after finishing a task. Wait for the explicit request.
Use this when the user says "review this PR", "valide esse PR" (pt-BR) or anything associated with the idea of validating a task.
| name | validate-task |
| description | Use when user says "validate the task", "ensure everything is passing", "is everything ok?", "valide a entrega" (PT-BR), "garanta que tudo está funcionando" (PT-BR), "certifique-se de que está tudo ok" (PT-BR), or anything associated with the idea of validating a task. |
First of all running the following commands before any check:
npm install
npm run build
composer install
Ensure the Laravel Pint is passing using:
./vendor/bin/pint --parallel --test
If pass successfully, proceed and check the next one. If you noticed any issue, ask if you can fix it.
Ensure the Eslint is passing using:
npm run lint
npm run build
If pass successfully, proceed and check the next one. If you noticed any issue, ask if you can fix it.
Ensure all tests are passing using:
./vendor/bin/pest --type-coverage --parallel --min=100
If pass successfully, proceed and check the next one. If you noticed any issue, ask if you can fix it.
Ensure all tests are passing using:
./vendor/bin/phpstan analyse --memory-limit=2G
If pass successfully, proceed and check the next one. If you noticed any issue, ask if you can fix it.
Ensure all tests are passing using:
./vendor/bin/pest --parallel --filter Feature
If pass successfully, proceed and check the next one. If you noticed any issue, ask if you can fix it.
Ensure all tests are passing using:
Do not run in parallel mode, otherwise this will cause problems with the browser tests. We need to run it in a single process. Also, run the tests filtering them whenever possible. Only in GitHub Actions do we run the entire suite of browser tests.
composer test:browser:ci
If pass successfully, proceed and check the next one. If you noticed any issue, ask if you can fix it.
If everything described above is correct, consider the delivery validated and ready. Use a green check mark icon to indicate this (✅). Feel free to draw a table with two columns: check and status, and then the indication of whether the check passed or failed.