How do I use the "Generate a Comprehensive Code Review Checklist" prompt?

Copy the prompt template, fill in the variables (PROGRAMMING_LANGUAGE, PROJECT_TYPE, TEAM_EXPERIENCE_LEVEL), and paste it into ChatGPT, Claude, or Gemini.

What AI tools work with this coding prompt?

This prompt works with chatgpt, claude, gemini. Simply copy and paste the template into any of these AI assistants.

Tips for getting the best results?

Customize the checklist for your team's specific coding standards and project requirements Start with a shorter checklist and gradually add items as your team becomes comfortable with the process Use this as a training tool for junior developers to learn what to look for in code reviews Consider creating separate checklists for different types of changes (bug fixes vs. new features) Review and update the checklist regularly based on common issues found in your codebase

coding intermediate

Generate a Comprehensive Code Review Checklist

Create thorough code review checklists tailored to your programming language and project type. Ensure code quality and consistency.

Works with: chatgptclaudegemini

Prompt Template

Act as a senior software engineer and create a comprehensive code review checklist for [PROGRAMMING_LANGUAGE] projects. The checklist should be tailored for [PROJECT_TYPE] and include both technical and non-technical review criteria. Structure the checklist into the following sections: 1. **Code Quality & Style** - Language-specific best practices - Naming conventions - Code formatting and consistency - Code complexity and readability 2. **Functionality & Logic** - Correctness of implementation - Edge case handling - Error handling and validation - Performance considerations 3. **Security & Safety** - Security vulnerabilities - Input validation - Authentication and authorization - Data protection 4. **Testing & Documentation** - Test coverage and quality - Code comments and documentation - API documentation - README and setup instructions 5. **Architecture & Design** - Design patterns usage - Code organization - Dependency management - Scalability considerations For each section, provide 4-6 specific, actionable checkpoints that reviewers can easily verify. Include brief explanations for why each point matters. Consider the experience level of [TEAM_EXPERIENCE_LEVEL] developers who will be using this checklist. Format the output as a clear, printable checklist with checkboxes that can be used during actual code reviews.

Variables to Customize

[PROGRAMMING_LANGUAGE]

The programming language for the code review

Example: Python

[PROJECT_TYPE]

Type of project being reviewed

Example: web API application

[TEAM_EXPERIENCE_LEVEL]

Experience level of the development team

Example: mid-level

Example Output

# Python Web API Code Review Checklist ## Code Quality & Style ☐ **PEP 8 Compliance**: Code follows Python style guidelines (line length, imports, spacing) ☐ **Naming Conventions**: Variables, functions, and classes use descriptive, pythonic names ☐ **Code Complexity**: Functions are focused and under 20 lines when possible ☐ **Import Organization**: Imports are grouped (standard, third-party, local) and unused imports removed ☐ **Type Hints**: Functions include appropriate type annotations for better code clarity ## Functionality & Logic ☐ **Requirements Met**: Code implements all specified functionality correctly ☐ **Edge Cases**: Handles empty inputs, null values, and boundary conditions ☐ **Error Handling**: Uses try-except blocks appropriately with specific exception types ☐ **HTTP Status Codes**: API endpoints return appropriate status codes (200, 404, 500, etc.) ☐ **Data Validation**: Input validation using libraries like Pydantic or marshmallow ## Security & Safety ☐ **SQL Injection**: Uses parameterized queries or ORM methods ☐ **Input Sanitization**: User inputs are validated and sanitized ☐ **Authentication**: Protected endpoints require proper authentication ☐ **Environment Variables**: Sensitive data (API keys, passwords) stored in environment variables ☐ **CORS Configuration**: Cross-origin requests properly configured ## Testing & Documentation ☐ **Unit Tests**: Critical functions have corresponding unit tests ☐ **API Documentation**: Endpoints documented with request/response examples ☐ **Docstrings**: Functions include clear docstrings explaining purpose and parameters ☐ **Code Comments**: Complex logic explained with inline comments ## Architecture & Design ☐ **Separation of Concerns**: Business logic separated from presentation layer ☐ **Database Connections**: Proper connection pooling and resource cleanup ☐ **Configuration Management**: Settings properly organized and configurable ☐ **Dependency Injection**: External services properly abstracted and testable

Pro Tips for Best Results

Customize the checklist for your team's specific coding standards and project requirements
Start with a shorter checklist and gradually add items as your team becomes comfortable with the process
Use this as a training tool for junior developers to learn what to look for in code reviews
Consider creating separate checklists for different types of changes (bug fixes vs. new features)
Review and update the checklist regularly based on common issues found in your codebase