// Lightweight PR-time audit for whether changes are compatible with the actual RAGAPPv3 GitHub Actions workflow, dependency lockfiles, scripts, and cross-platform local validation.
RAGAPPv3 engineering conventions — backend (FastAPI + SQLite + LanceDB), frontend (React + TypeScript + Vite + Vitest), database/migration/RBAC patterns, and the multi-agent skill layout. Load before implementing or refactoring backend routes/services/migrations or frontend pages/components, or when you need to know "how does this repo do X".
Apply when writing tests, modifying test files, fixing test failures, debugging CI failures, adding test coverage, creating adversarial tests, or reviewing any file under tests/. Also apply when implementing features or fixes that require corresponding test changes. Enforces framework-specific rules (bun:test for TypeScript, unittest/pytest for Python), mock isolation, cross-platform compatibility, and CI pipeline awareness. Load this skill before touching any test file.
RAGAPPv3 testing policy and conventions. Load before writing or modifying any test, fixing a test/CI failure, or adding coverage. Covers backend pytest + unittest (SimpleConnectionPool dependency-override harness, FK cascades, the Python 3.11-vs-local event-loop trap) and frontend Vitest + React Testing Library + jsdom (MemoryRouter, Radix Select, react-virtual mock patterns). This repo's frontend uses Vitest, NOT bun:test.
Run a graph-guided, tool-augmented Swarm PR review using context packing, parallel exploration, triggered plugin micro-lanes, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive tolerance and high recall.
Audit environment and configuration contracts across backend settings, frontend env usage, Docker, Compose, CI, docs, and examples. Use when changing config, deployment, root paths, CORS, settings schemas, env examples, or Docker files.
RAGAPPv3 subpath/reverse-proxy deployment system. Load before touching anything related to APP_ROOT_PATH, VITE_APP_BASENAME, VITE_API_URL, cookie paths, SPA catch-all routing, proxy configuration, or Docker build args for the frontend. Contains locked architectural decisions that must not be re-litigated.
| name | ci-compatibility-audit |
| description | Lightweight PR-time audit for whether changes are compatible with the actual RAGAPPv3 GitHub Actions workflow, dependency lockfiles, scripts, and cross-platform local validation. |
| effort | medium |
Use this skill before pushing workflow, dependency, test, build, lint, Docker, or tooling changes.
Primary workflow: .github/workflows/ci.yml
Frontend job:
cd frontendnpm ci --engine-strictnode --version, npm --version, npm ls vite vitest @vitejs/plugin-react jsdom, npm exec vite -- --version, and npm exec vitest -- --versionnpm run typechecknpm run lintnpm testnpm run buildVITE_APP_BASENAME=/knowledgevault and VITE_API_URL=/knowledgevault/apiBackend job:
cd backendpip install -r requirements-ci.txtpip install -r requirements-dev.txtruff check .pytest --tb=short -vRepository contract job:
python scripts/check_config_contract.pypython scripts/check_pr_scope_drift.pycd frontend && npm ci --engine-strict && npm run typecheck && npm run lint
cd frontend && npm test -- src/lib/api.test.ts src/lib/api.csrf.test.ts src/lib/api.sse.test.ts src/pages/WikiPage.sse.test.tsx src/stores/useAuthStore.api-base.test.ts
cd frontend && npm test && npm run build
cd frontend && VITE_APP_BASENAME=/knowledgevault VITE_API_URL=/knowledgevault/api npm run build
cd backend && ruff check . && pytest --tb=short -v
python scripts/check_config_contract.py
python scripts/check_pr_scope_drift.py
Run these before pushing so a CI-only lint/type failure doesn't cost a
push → fail → fixup-commit round trip. If frontend/node_modules is absent,
run npm ci --engine-strict first.
RuntimeError: There is no current event loop — the
test harness uses the removed implicit-event-loop pattern. These are false
failures from the local interpreter, not regressions. Prefer a 3.11 venv;
the ruff check . lint gate and CI-targeted tests are what matter.<Link>, driving Radix
Select, virtualized lists): see references/frontend-testing-gotchas.md
for the repo's established mock patterns before improvising.Classify each risk as:
BLOCKER: likely CI failure or invalid workflow.RISK: plausible CI instability requiring targeted validation.NOTE: useful context, not blocking.Include the exact workflow step or command for every item.