mcpField
C
code-reviewer

code-reviewer

github.com/nodnarbnitramTesting & quality16293 installsUpdated 27w ago
Repository

About code-reviewer

A code-review skill for developers that structures checks across quality, security, error handling, performance, and tests, then reports findings by severity.

Key features

  1. 01Code quality checklist
  2. 02Security and input checks
  3. 03Error and performance review
  4. 04Test coverage review
  5. 05Severity-based feedback

Use cases

  1. 01Reviewing a set of source files
  2. 02Finding security or validation issues
  3. 03Prioritizing fixes by severity

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nodnarbnitram/claude-code-extensions --skill code-reviewer

After installing, type/code-reviewerin Claude Code to confirm it loaded.

Details

From the project README

Code Reviewer

Perform comprehensive code reviews focusing on quality, security, and maintainability.

Instructions

  1. Read the target files using the Read tool
  2. Search for patterns and related code using Grep
  3. Find related files using Glob
  4. Analyze code against the review checklist
  5. Provide structured feedback with severity levels

Review Checklist

Code Quality
  • Code is simple and readable
  • Functions and variables are well-named
  • No duplicated code (DRY principle)
  • Appropriate comments for complex logic
  • Consistent code style
Security
  • No exposed secrets or API keys
  • Input validation implemented
  • SQL injection prevention
  • XSS prevention for web code
  • Proper authentication/authorization checks
Error Handling
  • Errors are caught and handled appropriately
  • Meaningful error messages
  • No silent failures
  • Proper logging for debugging
Performance
  • No obvious performance bottlenecks
  • Efficient algorithms and data structures
  • Appropriate caching where needed
  • Database queries are optimized
Testing
  • Adequate test coverage
  • Edge cases are tested
  • Tests are readable and maintainable

Output Format

Organize feedback by severity:

Critical (Must Fix)

Issues that could cause security vulnerabilities, data loss, or crashes.

Warning (Should Fix)

Issues that could cause bugs, poor performance, or maintenance problems.

Suggestion (Consider)

Improvements for readability, consistency, or best practices.

Example Feedback

### Critical
- **SQL Injection vulnerability** in `user_service.py:45`
  - User input passed directly to query without sanitization
  - Fix: Use parameterized queries

### Warning
- **Missing error handling** in `api_client.py:23`
  - Network errors will crash the application
  - Fix: Add try/catch with appropriate error response

### Suggestion
- Consider extracting the validation logic in `validators.py:78-95` into a separate function for reusability

Comments

Markdown supported