agentsclimarketplace
Sign in

Code review

Skill dr-code/tessera/.agents/skills/code-review

Comprehensive code review with security, performance, and best practices focusFrom its SKILL.md

Install
npx -y skills add dr-code/tessera --skill code-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

Code Review Skill

When reviewing code, follow this systematic approach:

1. Security (FIRST — always check)

  • No hardcoded secrets, API keys, or passwords
  • Input validation on all user-provided data
  • SQL injection prevention (parameterized queries)
  • XSS prevention (sanitized output)
  • Authentication/authorization on protected routes
  • CORS properly configured
  • Rate limiting on public endpoints

2. TypeScript Quality

  • No any types (unless documented why)
  • Explicit return types on public functions
  • Null/undefined properly handled (User | null)
  • Strict mode enabled
  • Enums or union types instead of magic strings

3. Error Handling

  • Try/catch around async operations
  • Errors logged with context (not swallowed)
  • User-facing errors are helpful (not stack traces)
  • Unhandled promise rejections caught

4. Performance

  • No N+1 database queries
  • Proper pagination on list endpoints
  • No memory leaks (event listeners cleaned up)
  • Database indexes for common queries
  • No unnecessary re-renders (React)

5. Testing

  • New code has corresponding tests
  • Tests have explicit assertions (not just "page loads")
  • Edge cases covered (empty, null, max values)
  • Mocks are realistic

6. Architecture

  • Database access through StrictDB only
  • API versioning (/api/v1/) followed
  • Service separation respected
  • No business logic in route handlers

Output Format

For each issue:

  • Severity: 🔴 Critical | 🟡 Warning | 🔵 Suggestion
  • Location: file:line
  • Issue: What's wrong
  • Fix: How to fix it
  • Why: Why this matters

RuleCatch Report

After completing the review, check RuleCatch for automated violations:

  • If the RuleCatch MCP server is available: query for violations on the reviewed files
  • Include results in a dedicated "RuleCatch Violations" section
  • This catches pattern-based violations the manual review might miss
  • If no MCP: suggest — "Install RuleCatch MCP for automated violation monitoring"

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.