code-review
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
Works with
---
name: code-review
description: Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
license: MIT
---
# Code Review Skill
Use this skill after implementing changes to validate your work before delivering.
## Review Checklist
### 1. Correctness
- [ ] Changes solve the original issue/task
- [ ] No unintended side effects on existing functionality
- [ ] Edge cases are handled
- [ ] Error handling is appropriate (not excessive)
### 2. Code Quality
- [ ] Code matches existing style and patterns
- [ ] No unnecessary complexity or abstraction
- [ ] Variable and function names are clear
- [ ] No dead code, commented-out code, or TODOs left behind
### 3. Tests
- [ ] New functionality has test coverage
- [ ] Existing tests still pass
- [ ] Tests cover both happy path and error cases
- [ ] Tests are not brittle (don't test implementation details)
### 4. Safety
- [ ] No hardcoded secrets or credentials
- [ ] User input is validated at boundaries
- [ ] No SQL injection, XSS, or command injection vectors
- [ ] File operations use safe paths
## Process
1. Read each modified file end-to-end (not just the diff)
2. Run the test suite: `execute("python -m pytest -v")`
3. Run linters if available: `execute("ruff check .")`
4. Run the bundled lint check: `execute("python /skills/code-review/lint_check.py .")`
5. Check against each item in the review checklist
6. If any issues found, fix them and re-review
7. When everything passes, the review is complete
## Helper Scripts
- **`/skills/code-review/lint_check.py`** — Scans Python files for missing
docstrings, long functions (>50 lines), and bare `except:` clauses. Run it
via `execute("python /skills/code-review/lint_check.py [path ...]")`.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.
