General Reviewer

git commit -m "fix"
git commit -m "updates"
git commit -m "WIP"
git commit -m "asdfasdf"

Mensajes de commit vagos hacen que el historial sea inútil

git commit -m "fix(auth): handle expired token refresh"
git commit -m "feat(api): add pagination to users endpoint"
git commit -m "docs: update README with new env vars"
git commit -m "refactor(db): extract query builders"

Sigue commits convencionales para un historial claro

src/
  UserComponent.tsx
  userUtils.ts
  USER_CONSTANTS.ts
  user-types.ts
  userApi.tsx      # Why .tsx for API?
  UserHelpers.ts

Nomenclatura inconsistente y estructura plana

src/features/users/
  components/
    UserCard.tsx
    UserList.tsx
  hooks/
    useUser.ts
  api/
    users.api.ts
  types/
    user.types.ts
  constants/
    user.constants.ts

Sigue organización basada en características con nomenclatura consistente

// Scattered across codebase
const API_URL = process.env.API_URL || 'http://localhost:3000'

// In another file
const apiBase = process.env.NEXT_PUBLIC_API_URL

// In yet another file
if (process.env.NODE_ENV === 'production') {
  baseUrl = 'https://api.example.com'
}

Variables de entorno dispersas, manejo inconsistente

// src/config/env.ts
export const config = {
  api: {
    baseUrl: requiredEnv('API_URL'),
    timeout: optionalEnv('API_TIMEOUT', 5000),
  },
  features: {
    analytics: boolEnv('ENABLE_ANALYTICS', false),
  },
} as const

// Usage everywhere
import { config } from '@/config/env'
fetch(config.api.baseUrl + '/users')

Configuración centralizada con acceso type-safe