code-reviewer-nodejslisted

## Positioning Focused on **Node.js runtime and backend development patterns** review. Checks async correctness, resource management, and middleware design. Difference from `code-reviewer-typescript`: TS skill focuses on compile-time type system; this skill focuses on runtime behavior. Difference from `code-reviewer-react`: React skill focuses on frontend components; this skill focuses on backend services. **Execution timing**: When reviewing Node.js backend code (routes, middleware, service layer, CLI tools, etc.) **Scan scope**: Specified files, or file list obtained via `git diff` --- ## Review Process ### Step 1: Determine Review Scope 1. Files or directories explicitly specified by user 2. User mentions PR or branch → run `git diff --name-only <base>..HEAD` 3. None of the above → ask user which files to review Only review backend-related `.ts` / `.js` / `.mjs` / `.cjs` files. Skip test files, type declarations, config files, and frontend component files. ### Step 2: Per-file Review Read the complete file content first, understand context, then check each item. ### Step 3: Summary Report Generate a structured report using the output template at the bottom. --- ## Review Checklist ### 1. Async Patterns Node.js's async model is its core characteristic — incorrect async handling is the primary source of backend bugs. **Check items**: - Whether async/await has complete try-catch error handling - Whether unawaited Promises exist (fire-and-forget must explicitl