code-review-checklist
Generate context-aware code review checklists from PR diffs — tailored to language, codebase patterns, and team standards. Identifies what reviewers should focus on. NOT for automated code
Works with
--- name: code-review-checklist description: Generate context-aware code review checklists from PR diffs — tailored to language, codebase patterns, and team standards. Identifies what reviewers should focus on. NOT for automated code license: MIT --- # Code Review Checklist Generator Generate thorough, contextual code review checklists that help reviewers focus on what matters most for each specific PR. ## When to Use - Before starting a code review to know what to look for - When onboarding new team members to review standards - To ensure consistent review quality across the team - When reviewing unfamiliar parts of the codebase ## Approach 1. **Analyze the Diff**: Understand what files changed and the nature of changes 2. **Identify Patterns**: Detect the type of change (feature, bugfix, refactor, etc.) 3. **Language-Specific Checks**: Apply relevant checks for the programming language 4. **Project Context**: Consider existing patterns and conventions in the codebase 5. **Generate Checklist**: Produce prioritized, actionable review items ## Checklist Categories ### Security - [ ] Input validation present - [ ] No hardcoded secrets or credentials - [ ] Proper authentication/authorization checks - [ ] SQL injection prevention - [ ] XSS prevention for web code ### Performance - [ ] No N+1 query patterns - [ ] Appropriate caching considered - [ ] No unnecessary loops or iterations - [ ] Efficient data structures used ### Maintainability - [ ] Code is readable and self-documenting - [ ] Functions are appropriately sized - [ ] No code duplication - [ ] Consistent naming conventions ### Testing - [ ] Unit tests cover new functionality - [ ] Edge cases are tested - [ ] Tests are meaningful, not just for coverage ## Best Practices - Prioritize security issues first - Focus on logic errors over style nitpicks - Consider the reviewer's time - highlight critical items - Adapt checklist to project maturity level
More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.
