testing-and-validation
PetSwipe validation workflow for choosing the smallest reliable checks for frontend, backend, infra, docs, and mixed changes. Use when a task needs a concrete validation plan or when the repo's pre-existing lint or type issues make broad validation noisy.
Datos de origen
- Repositorio
- hoangsonww/PetSwipe-Match-App
- Última actividad en el origen
- 28 de febrero de 2026 a las 02:14
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 26
- Forks
- 12
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Explorador de archivos
3 archivosMostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- testing-and-validation
- description
- PetSwipe validation workflow for choosing the smallest reliable checks for frontend, backend, infra, docs, and mixed changes. Use when a task needs a concrete validation plan or when the repo's pre-existing lint or type issues make broad validation noisy.
Use this skill when validation strategy matters as much as the code change.
## Workflow
1. Identify the touched area and its real blast radius.
2. Choose the smallest reliable checks that validate that area.
3. Prefer targeted checks before broad repo-wide checks.
4. Report clearly what each command validates.
5. Separate new failures from pre-existing repo debt.
## PetSwipe Guidance
- Frontend: prefer targeted `npx eslint` over broad linting when possible.
- Backend: prefer `npm run build` plus targeted tests.
- Infra: prefer render and preflight commands.
- Docs: validate by re-reading commands, paths, and claims against the repo.
If needed, spawn `test_guard` to recommend the validation set before editing.
Read `references/validation-playbook.md`.
Ver en GitHub