Files
github-copilot/site-fullstack/.github/skills/ecommerce-code-review/assets/react-review-matrix.md
T
ВяткинАртём 2817cf8dc6 Add test coverage checklist, report template, and stack matrix for ecommerce project
- Created a test coverage checklist to ensure comprehensive testing of backend and frontend components.
- Added a test report template to standardize reporting on test execution results and gaps.
- Introduced a test stack matrix to guide the selection of testing tools and frameworks for backend and frontend.
- Established a skill for repairing failing tests, including a failure triage checklist and a test repair template.
- Documented recommended MCP stack for ecommerce development with FastAPI and React/Next.js.
- Developed a detailed README outlining the project structure, agent capabilities, and recommended workflows.
- Compiled a comprehensive workflow guide detailing step-by-step commands for project setup, testing, and SEO implementation.
2026-05-20 18:09:24 +03:00

1.3 KiB

React Review Matrix

Configuration detection

  • Read package.json, tsconfig.json, ESLint config, framework config, and build setup.
  • Detect React version, Next.js version, TypeScript version, and testing setup.

Readability rules

  • Components should be easy to scan.
  • Props should be explicit and well named.
  • Business logic should not be buried in JSX noise.
  • Avoid deeply nested conditional rendering when a clearer structure would help.
  • Prefer predictable state flow over clever abstractions.

Modern React usage

  • Use modern React and framework features only when the installed version supports them and they improve maintainability.
  • Check whether newer APIs such as useEffectEvent, transitions, server components, or framework-native data loading would simplify the code.
  • Do not insist on useMemo or useCallback unless they are justified.
  • Avoid stale patterns if the installed version provides a clearer and safer replacement.

Harsh review checks

  • Unclear ownership of state.
  • Effect misuse.
  • Derived state bugs.
  • Excessive prop drilling when a better structure exists.
  • Over-componentization that hurts readability.
  • Poor separation between UI, data, and business rules.
  • Missing loading, empty, and error states.
  • Avoidable render churn and unstable object creation in hot paths.