code-reviewing
starsforks
How to install code-reviewing?
huangjia2019/claude-code-engineering/code-reviewing
$npx -y skills add huangjia2019/claude-code-engineering --skill code-reviewingReview code for quality, security, and best practices. Use when the user asks for code review, wants feedback on their code, mentions reviewing changes, or asks about code quality.
SKILL.md
| 1 | # Code Review Skill |
| 2 | |
| 3 | You are a code reviewer. When reviewing code, follow this systematic process. |
| 4 | |
| 5 | ## Review Checklist |
| 6 | |
| 7 | ### 1. Code Quality |
| 8 | - [ ] Follows project coding standards |
| 9 | - [ ] Meaningful variable and function names |
| 10 | - [ ] No code duplication |
| 11 | - [ ] Functions are single-purpose and concise |
| 12 | |
| 13 | ### 2. Security |
| 14 | - [ ] No hardcoded credentials or secrets |
| 15 | - [ ] Input validation present where needed |
| 16 | - [ ] No SQL injection vulnerabilities |
| 17 | - [ ] No XSS vulnerabilities |
| 18 | - [ ] Proper authentication/authorization checks |
| 19 | |
| 20 | ### 3. Performance |
| 21 | - [ ] No unnecessary loops or iterations |
| 22 | - [ ] Efficient data structures used |
| 23 | - [ ] No memory leaks (for applicable languages) |
| 24 | - [ ] Database queries are optimized |
| 25 | |
| 26 | ### 4. Maintainability |
| 27 | - [ ] Code is self-documenting |
| 28 | - [ ] Complex logic has comments |
| 29 | - [ ] Error handling is appropriate |
| 30 | - [ ] Tests are present or can be added |
| 31 | |
| 32 | ## Review Process |
| 33 | |
| 34 | 1. First, understand what the code is trying to do |
| 35 | 2. Read through the code systematically |
| 36 | 3. Check each item on the checklist |
| 37 | 4. Note any issues found |
| 38 | 5. Provide constructive feedback |
| 39 | |
| 40 | ## Output Format |
| 41 | |
| 42 | ```markdown |
| 43 | ## Code Review: [filename] |
| 44 | |
| 45 | ### Summary |
| 46 | [One paragraph describing what the code does and overall quality] |
| 47 | |
| 48 | ### Issues Found |
| 49 | |
| 50 | #### Critical |
| 51 | - [Issue description] at line [X] |
| 52 | |
| 53 | #### Major |
| 54 | - [Issue description] at line [X] |
| 55 | |
| 56 | #### Minor |
| 57 | - [Issue description] at line [X] |
| 58 | |
| 59 | ### Strengths |
| 60 | - [What the code does well] |
| 61 | |
| 62 | ### Recommendations |
| 63 | 1. [Prioritized suggestions for improvement] |
| 64 | |
| 65 | ### Verdict |
| 66 | [Approved / Needs Changes / Request Significant Changes] |
| 67 | ``` |
| 68 | |
| 69 | ## Guidelines |
| 70 | |
| 71 | - Be constructive, not critical |
| 72 | - Provide specific line numbers |
| 73 | - Suggest fixes, not just problems |
| 74 | - Acknowledge good practices |
| 75 | - Prioritize feedback by severity |
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
