Skip to content

Comprehensive Code Quality Review

Perform comprehensive code quality review

Instructions

Follow these steps to conduct a thorough code review:

  1. Repository Analysis
  2. Examine the repository structure and identify the primary language/framework
  3. Check for configuration files (package.json, requirements.txt, Cargo.toml, etc.)

  4. Review README and documentation for context

  5. Code Quality Assessment

  6. Scan for code smells, anti-patterns, and potential bugs
  7. Check for consistent coding style and naming conventions
  8. Identify unused imports, variables, or dead code

  9. Review error handling and logging practices

  10. Security Review

  11. Look for common security vulnerabilities (SQL injection, XSS, etc.)
  12. Check for hardcoded secrets, API keys, or passwords
  13. Review authentication and authorization logic

  14. Examine input validation and sanitization

  15. Performance Analysis

  16. Identify potential performance bottlenecks
  17. Check for inefficient algorithms or database queries
  18. Review memory usage patterns and potential leaks

  19. Analyze bundle size and optimization opportunities

  20. Architecture & Design

  21. Evaluate code organization and separation of concerns
  22. Check for proper abstraction and modularity
  23. Review dependency management and coupling

  24. Assess scalability and maintainability

  25. Testing Coverage

  26. Check existing test coverage and quality
  27. Identify areas lacking proper testing
  28. Review test structure and organization

  29. Suggest additional test scenarios

  30. Documentation Review

  31. Evaluate code comments and inline documentation
  32. Check API documentation completeness
  33. Review README and setup instructions

  34. Identify areas needing better documentation

  35. Recommendations

  36. Prioritize issues by severity (critical, high, medium, low)
  37. Provide specific, actionable recommendations
  38. Suggest tools and practices for improvement
  39. Create a summary report with next steps

Remember to be constructive and provide specific examples with file paths and line numbers where applicable.