code-review
installsforks
How to install code-review?
geeksfino/openskills/code-review
$npx -y skills add Geeksfino/openskills --skill code-reviewReviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.
SKILL.md
| 1 | # Code Review Skill |
| 2 | |
| 3 | Perform thorough code reviews following this methodology. |
| 4 | |
| 5 | ## Review Checklist |
| 6 | |
| 7 | ### 1. Correctness |
| 8 | - Does the code do what it's supposed to do? |
| 9 | - Are there any logic errors? |
| 10 | - Are edge cases handled? |
| 11 | |
| 12 | ### 2. Security |
| 13 | - Input validation and sanitization |
| 14 | - Authentication and authorization |
| 15 | - Sensitive data handling |
| 16 | - SQL injection, XSS, and other vulnerabilities |
| 17 | |
| 18 | ### 3. Performance |
| 19 | - Algorithm complexity |
| 20 | - Unnecessary computations |
| 21 | - Memory leaks or inefficient memory usage |
| 22 | - Database query optimization |
| 23 | |
| 24 | ### 4. Maintainability |
| 25 | - Code readability and clarity |
| 26 | - Appropriate naming conventions |
| 27 | - Single responsibility principle |
| 28 | - DRY (Don't Repeat Yourself) |
| 29 | |
| 30 | ### 5. Testing |
| 31 | - Test coverage |
| 32 | - Edge case testing |
| 33 | - Integration tests where appropriate |
| 34 | |
| 35 | ## Output Format |
| 36 | |
| 37 | Structure your review as: |
| 38 | |
| 39 | ``` |
| 40 | ## Summary |
| 41 | [One paragraph overview] |
| 42 | |
| 43 | ## Critical Issues |
| 44 | [Must fix before merge] |
| 45 | |
| 46 | ## Suggestions |
| 47 | [Nice to have improvements] |
| 48 | |
| 49 | ## Positive Observations |
| 50 | [What's done well] |
| 51 | ``` |
| 52 | |
| 53 | ## Guidelines |
| 54 | |
| 55 | - Be constructive, not critical |
| 56 | - Explain *why* something is an issue |
| 57 | - Suggest specific fixes when possible |
| 58 | - Acknowledge good patterns and practices |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
