# Devverse Validate

> Run repository-specific validation for DevVerse changes. Use when asked to test, validate, smoke check, or confirm modifications in this repository.

- Skill: `hoangsonww/devverse-validate` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add hoangsonww/devverse-validate`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hoangsonww/devverse-validate/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: hoangsonww (https://skillmd.com/u/hoangsonww)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hoangsonww/devverse-validate

---


# DevVerse Validation Workflow

1. Inspect the current diff first.
Use `git status --short` and `git diff --name-only`.

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 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 because of 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.