# Repository Validation

> Baseline validation sequence for repositories enrolled in the company engineering build service.

- Skill: `jacobragsdale/repository-validation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jacobragsdale/repository-validation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jacobragsdale/repository-validation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jacobragsdale (https://skillmd.com/u/jacobragsdale)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/jacobragsdale/repository-validation

---

# Repository validation contract

Read `engineering.toml` at the repository root before choosing validation commands. Its
`[validation]` entries are the reviewed source of truth consumed by the internal Build Service;
do not substitute similarly named commands from another repository.

Run the narrowest affected checks while iterating, then run every command listed in
`validation.required` before handoff. Generate no `quality-evidence.json` by hand: the Build
Service creates it from actual command results. If `engineering.toml` is absent, report the missing
enrollment contract and use documented repository commands without inventing company compliance.

Canonical reference: `ENG-BUILD-003`. Stop and ask the owning team before changing required checks,
generated-code verification, migration ordering, or release-policy fields.