review

Review TypeScript code changes for quality, security, and Better-T-Stack conventions.

Updated May 23, 2026
One-click install
npx skills add https://github.com/devturco/thiago-dev-template --skill review-devturco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/devturco/thiago-dev-template/tree/main/.claude/skills/review
Command: npx skills add https://github.com/devturco/thiago-dev-template --skill review-devturco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps prevent broken, insecure, or non-conforming code changes from reaching the main codebase by performing a disciplined review against your Better-T-Stack/CLAUDE.md conventions.

Core Features & Use Cases

  • Quality & correctness auditing: Checks type safety (e.g., avoiding any, ensuring Zod 4 usage) and validates tRPC input/schema patterns.
  • Security-focused review: Verifies auth protections and correct session/header handling for protected procedures and routes.
  • Architecture and conventions compliance: Ensures correct server/client boundaries, error handling with TRPCError, and Biome/style adherence.
  • Performance and data access review: Looks for Suspense/query correctness, mutation invalidation, and Drizzle/DB query best practices to avoid N+1 and unsafe patterns.

Quick Start

Review the recent code changes in this repository for quality, security, and alignment with CLAUDE.md conventions and return a verdict with categorized findings.

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code changes for tRPC and Zod 4 validation patterns?

To review tRPC input patterns and verify Zod 4 schema validation, this Skill audits TypeScript modifications against Better-T-Stack conventions, checking type safety and enforcing strict validation rules to prevent broken or insecure code from merging.

What is the best way to enforce server/client boundaries in a Better-T-Stack repository?

Enforcing server/client boundaries involves auditing your code modifications against CLAUDE.md conventions to verify React data fetching, protected auth procedures, and TRPCError handling comply with your Better-T-Stack architectural rules.

How do I check Drizzle ORM queries for performance issues like N+1?

Checking Drizzle ORM queries involves reviewing data access patterns and mutation invalidations to identify and avoid N+1 problems. This safeguards database performance by ensuring your queries follow Drizzle best practices during code review.

Does this code review process verify Better-Auth session and header handling?

Yes, the code review verifies Better-Auth session and header handling by checking protected procedures and routes for correct auth protections. This security-focused review ensures session management aligns with your defined conventions.

Can I use this to audit Biome compliance and TRPC error handling together?

Yes, you can audit Biome compliance and TRPC error handling together by reviewing code changes for architecture adherence. This verifies errors use TRPCError correctly while maintaining your specified Biome style and formatting rules.

When do I need to review Suspense and React data fetching correctness?

You need to review Suspense and React data fetching correctness when modifying client-side data access in a Better-T-Stack setup. This ensures queries handle loading states properly and follow required server/client boundary conventions.