Run the full test suite (ruff + all layers), fix failures, then draft and commit with a human-readable message. Use when the user asks for a commit message, wants help summarizing changes before committing, or before running git commit.
Run and fix backend pytest tests after API, scanner, model, or router changes. Use when modifying backend/app/, adding endpoints, or when API tests fail.
Run Vitest component tests after React component or page changes. Use when modifying frontend/src/ components, pages, or api.js mocks.
Bump VERSION, sync E2E version checks, run the full test suite, and commit only if green — then tag and publish VLCouchSetup.exe. ALWAYS use this skill when the user mentions version, release, bump, semver, tag, ship, publish, next version, prepare release, or cutting a release — even vague one-line prompts.
Run Playwright E2E browser tests to verify UI flows end-to-end. Use before declaring work complete, after UI flow changes, or when browser behavior must be validated.
Keep AGENTS.md, selector rules, verify skills, and CONTRIBUTING.md in sync with code. Use after adding or changing data-testid values, API endpoints, env vars, test file locations, project structure, or verification commands.
End-to-end recipe for adding a new API endpoint — router, tests, api.js, UI, and verification. Use when implementing a new backend route that the frontend will call.
Run scanner and library-scan tests after changes to file parsing, scan orchestration, or fixture media. Use when modifying scanner.py, library_scan.py, genre_tags.py, or backend/tests/fixtures/media/.