Code Review
SkillSecurityReview code changes for bugs, security issues, performance problems, and style violations. Use when asked to review code, a PR, or recent changes.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Code Review skill
What this skill tells your AI
The instructions your AI receives, as published by owainlewis/youtube-tutorials in tutorials/pi-coding-agent-guide/resources/04-skills/code-review/SKILL.md and read by ahel’s 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.
Signals
- GitHub stars
- 385
- Forks
- 79
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
code-review-owainlewis- Source
- github.com/owainlewis/youtube-tutorials