create-review-checklist

Code review checklists are generated by detecting the type of change in your PR—whether it's Mojo code, Python, tests, or documentation—then outputting category-specific checks prioritized by impact. Extract changed files with `gh pr diff <pr> --name-only`, then pipe the diff to the Skill to receive structured, prioritized checklists that guide reviewers on what to focus on.

The checklist supports Mojo, Python, Markdown documentation, and test files. It detects four change types—code-only, test-only, docs-only, and multi-type changes—and generates tailored recommendations for each, ensuring reviewers check language-specific issues, test coverage, documentation accuracy, and cross-file consistency.

Yes, the Skill generates category-specific checklists for both Mojo and Python files in the same PR. It applies separate templates and recommendations for each language, allowing teams working with both to get language-appropriate guidance without manual customization.

The Skill uses change-type detection from PR diffs to identify which files changed, classifies them by language and purpose, selects matching templates for code, tests, docs, or mixed changes, then outputs prioritized, category-specific checks that address the most relevant concerns for that change type.

Use the structured, prioritized checklist as a guide for your review process. The checklist organizes checks by category and impact level, helping you focus on the most critical items first and ensuring you don't miss language-specific or change-type-specific issues relevant to Mojo, Python, tests, or documentation.