code-review-helper
Code Review Helper
A skill for conducting thorough code reviews with actionable feedback.
When to Use
- Reviewing pull requests or code changes
- Checking code for bugs, security issues, or performance problems
- Ensuring code follows best practices and project conventions
- Providing constructive feedback on code quality
Review Process
Step 1: Gather Context
Before reviewing, gather relevant context:
- Read the PR description or commit message to understand the intent
- Check if there's a CLAUDE.md or similar project documentation
- Identify the files that were changed
- Understand the scope of changes
Step 2: Analyze Changes
For each changed file, analyze:
- Correctness: Does the code do what it's supposed to do?
- Security: Are there any security vulnerabilities?
- Performance: Are there inefficient patterns or bottlenecks?
- Maintainability: Is the code readable and well-structured?
- Testing: Are there adequate tests?
- Documentation: Is the code appropriately documented?
Step 3: Provide Feedback
Structure feedback using these categories:
- Critical: Must fix before merge (bugs, security issues)
- Warning: Should fix (performance, maintainability)
- Suggestion: Nice to have (style, refactoring)
- Question: Need clarification
Review Checklist
General
- Code follows project conventions
- No obvious bugs or logic errors
- Error handling is appropriate
- No hardcoded secrets or credentials
Security
- Input validation is present
- SQL injection is prevented
- XSS vulnerabilities are addressed
- Command injection is prevented
- No sensitive data in logs
Performance
- No N+1 queries
- Expensive operations are optimized
- Caching is used appropriately
- Memory usage is reasonable
Maintainability
- Functions are appropriately sized
- Naming is clear and consistent
- Code is DRY (Don't Repeat Yourself)
- Comments explain "why", not "what"
Additional Resources
references/security-patterns.md- Common security patterns and anti-patternsreferences/performance-guide.md- Performance review guidelinesscripts/generate-review-summary.py- Generate a review summary
More from 4444zyf/skills
github-repo-analyzer
|
25email-sender
Send emails with folder attachments via SMTP. Use this skill when the user wants to send files or folders via email, share directories as compressed attachments, or email backup archives. Automatically triggers when users mention sending emails with attachments, emailing folders, or compressing and sending files.
2project-analyzer
This skill should be used when the user asks to "analyze project", "understand codebase", "explore project structure", "analyze architecture", "what does this project do", or needs help understanding an unfamiliar codebase.
1git-commit-assistant
This skill should be used when the user asks to "commit changes", "write commit message", "create a commit", "stage files", or needs help with git commit workflow including writing meaningful commit messages.
1