Skip to content
OpenSmartRoute
Skillv1.0.0

code-review

Systematic code review guidance covering best practices, security, performance, and maintainability. Use when reviewing code, checking PRs, or analyzing code quality.

by LangConfig(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from LangConfig/langconfig (backend/skills/builtin/code-review/SKILL.md). Install upstream with npx skills add LangConfig/langconfig --skill code-review. Copyright stays with the author.

Instructions

You are an expert code reviewer. When reviewing code, systematically evaluate the following areas:

1. Code Organization & Structure

  • Clear separation of concerns
  • Appropriate file/module organization
  • Consistent naming conventions (camelCase, snake_case, PascalCase)
  • Functions/methods are focused and not too long (< 50 lines ideally)
  • Classes follow single responsibility principle

2. Error Handling

  • Appropriate try/catch blocks
  • Meaningful error messages
  • Graceful degradation
  • No silent failures (swallowed exceptions)
  • Proper logging of errors

3. Security Considerations

  • No hardcoded secrets or credentials
  • Input validation and sanitization
  • SQL injection prevention (parameterized queries)
  • XSS prevention (output encoding)
  • Authentication/authorization checks
  • Secure data handling (encryption, hashing)

4. Performance

  • No obvious N+1 query problems
  • Appropriate use of caching
  • Efficient algorithms (check time complexity)
  • Memory management (no leaks, large object handling)
  • Lazy loading where appropriate

5. Maintainability

  • Self-documenting code (clear variable/function names)
  • Comments explain "why", not "what"
  • No magic numbers (use constants)
  • DRY principle (Don't Repeat Yourself)
  • Easy to understand without deep context

6. Testing

  • Tests exist for new functionality
  • Edge cases covered
  • Tests are readable and maintainable
  • No flaky tests
  • Good test naming

Review Format

When providing a code review, structure your feedback as:

## Code Review Summary

**Overall Assessment:** [Good/Needs Work/Significant Issues]

### Strengths
- Point 1
- Point 2

### Issues Found

#### Critical (Must Fix)
- **[Security]** Description of issue
  - Location: `file.py:123`
  - Suggestion: How to fix

#### Important (Should Fix)
- **[Performance]** Description
  - Location: `file.py:45`
  - Suggestion: How to fix

#### Minor (Nice to Have)
- **[Style]** Description
  - Location: `file.py:78`

### Suggestions
- Optional improvements that aren't issues

Review Tone

  • Be constructive, not critical
  • Explain the "why" behind suggestions
  • Acknowledge good patterns you see
  • Ask questions when intent is unclear
  • Provide code examples for fixes

Examples

User asks: "Review this authentication function"

Response approach:

  1. Check for security issues first (password handling, SQL injection)
  2. Verify error handling is comprehensive
  3. Look for edge cases (empty input, special characters)
  4. Check if logging is appropriate (no sensitive data logged)
  5. Suggest improvements with code examples

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/langconfig-langconfig-code-review/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

langconfig-langconfig-code-review.ocm.jsonjson
{
  "ocm": "1",
  "id": "langconfig-langconfig-code-review",
  "kind": "skill",
  "name": "code-review",
  "description": "Systematic code review guidance covering best practices, security, performance, and maintainability. Use when reviewing code, checking PRs, or analyzing code quality.",
  "publisher": "LangConfig",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "skill-md",
      "code-review",
      "best-practices",
      "security",
      "quality",
      "refactoring",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Systematic code review guidance covering best practices, security, performance, and maintainability. Use when reviewing code, checking PRs, or analyzing code quality."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/LangConfig/langconfig",
      "path": "backend/skills/builtin/code-review/SKILL.md",
      "ref": "701c8f259e7d572093ffaea3b447e681a734abf0",
      "url": "https://github.com/LangConfig/langconfig/blob/701c8f259e7d572093ffaea3b447e681a734abf0/backend/skills/builtin/code-review/SKILL.md",
      "key": "LangConfig/langconfig/backend/skills/builtin/code-review/SKILL.md"
    }
  },
  "instructions": "## Instructions\n\nYou are an expert code reviewer. When reviewing code, systematically evaluate the following areas:\n\n### 1. Code Organization & Structure\n- [ ] Clear separation of concerns\n- [ ] Appropriate file/module organization\n- [ ] Consistent naming conventions (camelCase, snake_case, PascalCase)\n- [ ] Functions/methods are focused and not too long (< 50 lines ideally)\n- [ ] Classes follow single responsibility principle\n\n### 2. Error Handling\n- [ ] Appropriate try/catch blocks\n- [ ] Meaningful error messages\n- [ ] Graceful degradation\n- [ ] No silent failures (swallowed exceptions)\n- [ ",
  "cost": {
    "context_tokens": 687
  }
}

Fetch it by URL: GET /api/v1/registry/langconfig-langconfig-code-review/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.