devverse-validate
Run repository-specific validation for DevVerse changes. Use when asked to test, validate, smoke check, or confirm modifications in this repository.
Datos de origen
- Repositorio
- hoangsonww/DevVerse-SWE-Blog
- Última actividad en el origen
- 28 de febrero de 2026 a las 11:47
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 15
- Forks
- 13
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
2 archivosMostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- devverse-validate
- description
- Run repository-specific validation for DevVerse changes. Use when asked to test, validate, smoke check, or confirm modifications in this repository.
- argument-hint
- ["scope"]
- disable-model-invocation
- true
# DevVerse Validation Workflow
Validate the current change set for `$ARGUMENTS`.
1. Inspect the current diff first.
Use `git status --short` and `git diff --name-only` to understand what changed.
2. Read the validation matrix before running commands.
@references/validation-matrix.md
3. Choose the smallest useful set of validations that matches the touched files.
4. Never use `npm run lint` as a read-only validation step.
It runs Prettier write mode in this repository.
5. Prefer the constrained-environment Jest commands when needed.
Use `env JEST_USE_WATCHMAN=0 npm test -- --runInBand --watchman=false`.
6. Run `python3 .claude/scripts/check_content_contract.py` for article changes.
7. Run `npx tsc --noEmit --pretty false` for TypeScript, route, component, or library changes.
8. Run `npm run build` for page, layout, config, or global styling changes when it is worth the extra cost.
If it fails due Google font fetching, report that as an environment limitation unless there is evidence of a code regression.
9. Report exactly what ran, what passed, what failed, and what was skipped.
Ver en GitHub