Resolving dependencies
Resolved, downloaded and extracted [2]
  
Agent guidance
  - Treat React Doctor diagnostics as starting hypotheses. Read the relevant code before confirming or suppressing each finding.
  - For each group, decide true positive, false positive, or needs-human-review, then assign high/medium/low confidence.
  - Do not suppress a finding without evidence from the file in question. Confidence requires code context.
  - Understand the root cause before editing. Fix the underlying code instead of changing react-doctor config or suppressing rules unless explicitly asked.
  - Investigate deeply where relevant: race conditions, security-sensitive flows, state propagation, multi-file refactors, and downstream dependency chains.
  - Ignore pure style preferences, theoretical issues without real impact, missing features, and unrelated pre-existing code.
  - Start with high-confidence fixes that preserve behavior. Leave low-confidence or product-dependent changes as notes.
  - Run `npx react-doctor@latest --verbose --scope changed` before and after changes, plus relevant tests after each focused batch.
  - When available, spawn subagents or isolated worktrees for independent rule families, then review and merge only the best safe fixes.
  - Split unrelated, broad, or behavior-changing work into separate PRs/branches instead of one large cleanup.
  - When one rule spans dozens of files (a migration-scale change), fix a representative sample first, confirm the recipe holds, and get the code owner's sign-off before changing the rest. Don't mass-fix a broad pattern in one unreviewed pass.
  - For confirmed issues that cannot be fixed now, create GitHub issues with the rule, file/line, confidence, impact, and proposed fix.
  - If a fix needs an API, UX, or architecture decision, stop and ask before editing.

✔ Scanned 34 files in 1.5s

React Doctor — @packages/db_helper_postgres
Score disabled by --no-score. Want something custom to your company? Contact us at https://react.doctor/enterprise.

27 issues
Performance: 21 warnings
Bugs: 6 warnings

⚠ await inside a loop ×21
  react-doctor/async-await-in-loop
  src/admin-apis/const.ts:18
  src/admin-apis/order.ts:596
  src/admin-apis/order.ts:600
  src/admin-apis/slots.ts:192
  src/admin-apis/slots.ts:267
  src/db/porter.ts:36
  src/db/porter.ts:54
  src/db/porter.ts:72
  src/db/porter.ts:90
  src/db/seed.ts:19
  src/db/seed.ts:31
  src/db/seed.ts:43
  src/db/seed.ts:66
  src/db/seed.ts:81
  src/db/seed.ts:125
  src/lib/seed.ts:15
  src/lib/seed.ts:31
  src/lib/seed.ts:47
  src/lib/seed.ts:67
  src/lib/seed.ts:100
  src/user-apis/auth.ts:215
⚠ Sequential independent awaits ×6
  react-doctor/server-sequential-independent-await
  src/admin-apis/product.ts:129
  src/admin-apis/product.ts:238
  src/db/seed.ts:55
  src/db/seed.ts:59
  src/db/seed.ts:61
  src/user-apis/product.ts:107
  Full diagnostics written to /var/folders/6t/3blzq7_j6p95xzry6t7c14hw0000gn/T/react-doctor-b58ef157-fc87-44ee-9be7-5224edb5c8d7

  ────────────────────────────────────────────────────────────

  Docs: https://react.doctor/docs
  Learn more about fixing issues, setting up CI/CD, and
  configuring rules with a config file

  GitHub: https://github.com/millionco/react-doctor
  Report issues and star the repository!


React Doctor is not installed in this project.
Ask the user if they would like to set it up, then run:

  npx react-doctor install --yes

This adds agent skill files, a `doctor` package script, and react-doctor as a dev dependency.
