grocery-app/.agents/skills/fiddy-verify/SKILL.md

name	description
fiddy-verify	Run and report the Fiddy repository verification loop. Use when Codex is finishing changes, checking repo health, validating docs/scripts/config updates, or deciding which lint/typecheck/test/build commands are appropriate for this Express/Vite/npm project.

Fiddy Verification

Use this workflow from the repo root.

Before Running Commands

• Read AGENTS.md, PROJECT_INSTRUCTIONS.md, and any doc related to the touched area.
• Check git status --short --branch so user work is not mistaken for Codex changes.
• Do not print real .env values. Inspect keys only if environment context is needed.
• Do not run DB migrations unless the user explicitly asked for migration execution.

Choose Checks

• Docs-only changes: validate affected Markdown links/content where practical, then run JSON/script sanity checks if package files changed.
• Root or frontend script changes: run npm run lint, npm run typecheck, and the relevant build command.
• Backend behavior changes: run npm test; add focused Jest/Supertest coverage for changed API behavior.
• Frontend behavior changes: run npm run lint, npm run typecheck, and focused Playwright tests when a browser flow changed.
• Dependency or lockfile changes: run npm run audit after install/update commands.
• Migration changes: run npm run db:migrate:stale:check and npm run db:migrate:verify only against the intended external DB environment.

Default Safe Loop

Run these when dependencies are already installed and the touched files justify them:

npm run lint
npm run typecheck
npm run audit
npm test
npm run build:backend
npm run build:frontend

Report

• List exact commands run and pass/fail.
• For failures, include the short relevant error and whether it appears caused by the current changes.
• If a check is skipped, state the concrete reason.
• End with unresolved risks and the smallest useful next step.