Name: Full Repo Validation
Author: Hamzha

Use this when the task is to make the whole repo pass its standard checks, not just a single feature area.

Workflow

Inspect git status --short so you understand existing local changes before editing.
From the repo root, run the full checks in this order: npm run lint, npm run build, npm run test.
Treat the first failing command as the active constraint. Read the full error, identify the root cause, and make the smallest defensible fix.
After each edit, run the narrowest relevant validation first, such as npm run lint -- --filter=<workspace>, npm run build -- --filter=<workspace>, or npm run test -- --filter=<workspace>.
Once the local fix is green, rerun the full command that previously failed.
Continue until all three full-repo commands pass, or until you hit a real external blocker such as missing credentials or unavailable services.
Finish by formatting changed TypeScript and Markdown files, then rerun any full checks affected by that formatting.

Standards

Use this when the task is to make the whole repo pass its standard checks, not just a single feature area.

Inspect git status --short so you understand existing local changes before editing.
From the repo root, run the full checks in this order: npm run lint, npm run build, npm run test.
Treat the first failing command as the active constraint. Read the full error, identify the root cause, and make the smallest defensible fix.
After each edit, run the narrowest relevant validation first, such as npm run lint -- --filter=<workspace>, npm run build -- --filter=<workspace>, or npm run test -- --filter=<workspace>.
Once the local fix is green, rerun the full command that previously failed.
Continue until all three full-repo commands pass, or until you hit a real external blocker such as missing credentials or unavailable services.
Finish by formatting changed TypeScript and Markdown files, then rerun any full checks affected by that formatting.