Code Review Guide

Before You Start

Leftover
```
console.log
```
/
```
console.debug
```
— should use
```
debug
```
package or remove
Missing
```
return await
```
in try/catch — see https://typescript-eslint.io/rules/return-await/ (not in our ESLint config yet, requires type info)
Can the fix/implementation be more concise, efficient, or have better compatibility?

Keys added to

src/locales/default/{namespace}.ts

with

{feature}.{context}.{action|status}

naming

Newly written code duplicates existing utilities in
```
packages/utils
```
or shared modules?
Copy-pasted blocks with slight variation — extract into shared function
```
antd
```
imports replaceable with
```
@lobehub/ui
```
wrapped components (
```
Input
```
,
```
Button
```
,
```
Modal
```
,
```
Avatar
```
, etc.)
Use
```
antd-style
```
token system, not hardcoded colors

A downstream cloud deployment depends on this repo. Flag changes that may require cloud-side updates:

Backend route paths changed — e.g., renaming
```
src/app/(backend)/webapi/chat/route.ts
```
or changing its exports
SSR page paths changed — e.g., moving/renaming files under
```
src/app/[variants]/(auth)/
```
Dependency versions bumped — e.g., upgrading
```
next
```
or
```
drizzle-orm
```
in
```
package.json
```
@lobechat/business-*
exports changed — e.g., renaming a function in
```
src/business/
```
or changing type signatures in
```
packages/business/
```
```
src/business/
```
and
```
packages/business/
```
must not expose cloud commercial logic in comments or code

For local CLI review only (GitHub review app posts inline PR comments instead):

Number all findings sequentially
Indicate priority:
```
[high]
```
/
```
[medium]
```
/
```
[low]
```
Include file path and line number for each finding
Only list problems — no summary, no praise
Re-read full source for each finding to verify it's real, then output "All findings verified."