Code review
Skill owainlewis/youtube-tutorials/tutorials/pi-coding-agent-guide/resources/04-skills/code-review
All my YouTube tutorials. Everything here is free - but please follow me on YouTube if you find these helpful. ❤️
npx -y skills add owainlewis/youtube-tutorials --skill code-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
Review code changes for bugs, security issues, performance problems, and style violations. Use when asked to review code, a PR, or recent changes.
SKILL.md
1.3 KB, as published. Nobody here has run it
Code Review
When reviewing code, follow this process:
Step 1: Understand the Change
Run git diff (or git diff --staged for staged changes) to see what changed.
Read the modified files in full to understand the surrounding context.
Step 2: Check for Issues
Review each changed file for:
Correctness
- Logic errors, off-by-one errors, race conditions
- Missing null/undefined checks at system boundaries
- Incorrect error handling (swallowed errors, wrong error types)
Security
- SQL injection, XSS, command injection
- Hardcoded secrets or credentials
- Overly permissive file/network access
Performance
- N+1 queries, unnecessary loops, large allocations
- Missing indexes for new database queries
- Blocking operations in async code
Maintainability
- Unclear naming, overly complex logic
- Dead code, unused imports
- Missing types in TypeScript
Step 3: Report
Format your review as:
- Summary: One sentence on what the change does
- Issues: Specific problems with file paths and line numbers
- Suggestions: Optional improvements (clearly marked as optional)
Be direct. Don't pad with praise. Focus on things that matter.