review▌

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Follow these guidelines when reviewing code for Sentry projects.

Simple, pragmatic, opinionated. Only what matters for writing production-grade SQLAlchemy and Alembic code.

Code review framework following Sentry engineering practices for pull requests and code quality assessment. \n \n Covers six key problem areas: runtime errors, performance bottlenecks, side effects, backwards compatibility, ORM query issues, and security vulnerabilities \n Includes design assessment guidance for component interactions, architectural alignment, and requirement conflicts \n Requires appropriate test coverage across functional, integration, and end-to-end tests with verification of

Structured logging for TypeScript/JavaScript with framework-agnostic setup, wide events, and drain adapters. \n \n Supports 12+ frameworks: Nuxt, Next.js, SvelteKit, Nitro, TanStack Start, NestJS, Express, Hono, Fastify, Elysia, Cloudflare Workers, and standalone TypeScript \n Detects and refactors console.log spam and unstructured errors into self-documenting wide events with grouped context \n Includes drain adapters for Axiom, OTLP, PostHog, Sentry, Better Stack, and file system; supports bat

Comprehensive security checklist covering secrets, input validation, authentication, and deployment readiness. \n \n Covers 10 critical security domains: secrets management, input validation, SQL injection prevention, authentication/authorization, XSS prevention, CSRF protection, rate limiting, sensitive data exposure, blockchain wallet verification, and dependency security \n Includes code examples for both unsafe and secure patterns across TypeScript, SQL, and configuration files \n Provides p

When running a security review on a codebase, follow these structured steps to identify potential vulnerabilities, leaks, and misconfigurations.

Catches common bugs in LangGraph state management, graph structure, and async patterns. \n \n Identifies 20+ critical issues including state mutations, missing reducers, invalid conditional edge returns, and checkpointer configuration errors \n Covers state schema problems like improper use of add_messages , full-state returns, and Pydantic models without annotations \n Detects graph structure issues: missing entry points, unreachable nodes, incomplete conditional paths, and undeclared Command d

$1f

Build an HTML page that loads traces from a data source (JSON/CSV file), displays one trace at a time with Pass/Fail buttons, a free-text notes field, and Next/Previous navigation. Save labels to a local file (CSV/SQLite/JSON). Then customize to the domain using the guidelines below.