代码审查检查表生成器

Linters catch syntax and formatting issues automatically. This checklist covers higher-level concerns that require human judgment: architectural decisions, business logic correctness, security implications, performance trade-offs, and test quality. It complements linters rather than replacing them.

Use 'General' for everyday pull requests to get broad coverage. Use a specific focus (Security, Performance, Architecture, Testing) when the change has particular risk in that area — e.g., Security focus for authentication changes, Performance focus for database query changes.

Yes. The generated checklist is a comprehensive starting point. Remove items that do not apply to your stack, add team-specific conventions, and save the result as your team's official code review template.

Each language has unique checks: TypeScript strict mode and type safety, Python type hints and async patterns, Java null safety and stream usage, Go error handling and goroutine leaks, Rust ownership and lifetime patterns, PHP type declarations and SQL injection patterns.

Solo checklists focus on self-review discipline and common blind spots. Small team checklists add communication items (PR descriptions, commit messages). Large team checklists include process governance, cross-team impact assessment, and documentation requirements.

Absolutely. Copy the generated Markdown checklist into your repository's .github/PULL_REQUEST_TEMPLATE.md file. Reviewers can check off items as they review, creating a consistent and auditable review process.