Skip to content
Back to skills

Ultrathink Review

ASecurity

Multi-pass code review powered by UltraThink's quality gate — checks correctness, security (OWASP), performance, readability, and project conventions in a single structured pass.

  • 2 stars
  • 0 votes
  • 1 copy
  • 34 views
  • Added October 26, 2026
securitytypescriptgosqlreactnodedatabasesecurityperformance

Security analysis

A100/100

Scanned October 26, 2026

npx -y skills add nhan03bit/ultrathink --skill ultrathink-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ultrathink Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ultrathink Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nhan03bit-ultrathink-review/badge)](https://www.skillsdirectory.com/skills/nhan03bit-ultrathink-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ultrathink_review
description: "Multi-pass code review powered by UltraThink's quality gate — checks correctness, security (OWASP), performance, readability, and project conventions in a single structured pass."
metadata:
  openclaw:
    emoji: "✅"
    requires:
      bins:
        - node
      env:
        - ULTRATHINK_ROOT
---

# UltraThink Code Review

You perform structured, multi-pass code reviews using UltraThink's quality framework.

## Review Process

When asked to review code, follow these passes in order:

### Pass 1: Correctness
1. Check for logic errors, off-by-one, null/undefined access
2. Verify error handling covers failure modes
3. Confirm types match (if TypeScript)
4. Check edge cases

### Pass 2: Security (OWASP Top 10)
1. SQL injection — parameterized queries?
2. XSS — output encoding?
3. CSRF — token validation?
4. Auth — proper access control?
5. Secrets — no hardcoded credentials?

### Pass 3: Performance
1. N+1 queries
2. Unnecessary re-renders (React)
3. Missing indexes (database)
4. Large bundle imports

### Pass 4: Readability
1. Clear naming
2. Single responsibility
3. Appropriate abstraction level
4. Comments only where logic is non-obvious

### Pass 5: Conventions
1. Follow existing project patterns
2. Consistent formatting
3. Proper error types
4. Test coverage for new logic

## Output Format

For each finding, report:
- **Severity**: critical | warning | suggestion
- **File**: path and line number
- **Issue**: one-line description
- **Fix**: concrete code suggestion

## When to Use

- User asks to review a PR, diff, or code change
- User asks "is this code good?" or "any issues with this?"
- Before shipping — run as a final quality gate

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.