`REVIEW_PROMPT.txt`

33 lines

You are reviewing a project that belongs to Steve, a solo operator running a wallcoverings business and a portfolio of side projects. Read the project's source code in the current working directory and produce a CRITICAL code review.

OUTPUT FORMAT (markdown, terse, no fluff):

## Snapshot
- One-line description of what this project is (infer from code/configs/READMEs).
- Stack: languages, frameworks, runtime, datastore.
- How it's run: pm2 / systemd / launchd / cron / manual / unclear.
- Status: live / stale / abandoned (justify in <10 words).

## Top Risks (P0 — fix this week)
Bullet each risk with: file:line if applicable, the concrete failure mode, and the fix in <2 lines.
Focus on: secrets leaked in code, broken auth, SQL injection, missing input validation on user routes, race conditions in jobs, missing error handling that silently drops data, hardcoded prod credentials, dependencies with known CVEs (when obvious from package files).

## Notable Issues (P1 — fix this month)
Same format. Cover: dead code paths, untested critical paths, performance footguns (N+1, sync I/O in hot loops), confusing module layout that will bite a future maintainer, inconsistent error handling.

## Polish (P2 — when convenient)
Style/structure improvements, missing tests, missing docs.

## Strengths
Two or three things worth keeping/extending. Be specific.

## Open questions for the owner
Three or fewer questions whose answers would change your recommendations.

CONSTRAINTS:
- Be concrete. Cite files and line numbers where possible.
- Do not invent issues. If a category has nothing, write "none observed".
- Skip generic advice ("add tests", "use TypeScript") unless the absence is actively causing risk.
- Cap total output at ~600 words.
- Do not modify any files. Read-only.