.claude/skills/validate-task-development/SKILL.md
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.
npx skillsauth add tallstackui/tallstackui validate-taskInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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:
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.
testing
Use this when the user says "review this PR", "valide esse PR" (pt-BR) or anything associated with the idea of validating a task.
testing
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
testing
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).
testing
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".