Review or remove evidence-backed redundant code and commentary within an authorized scope while preserving behavior. Use for a focused cleanup after implementation or before review, not feature work or logic fixes.
Compare the selected API specification with actual route, handler, validation, and serialization contracts. Report verified drift, complete scoped agreement, or unverified coverage without changing code or specs.
Assess architecture choices, feasibility, and trade-offs for structural changes, integrations, or consequential design decisions. Use before implementation or when an approach needs reconsideration.
Review backend SQL safety, error handling, API contracts, authorization, sensitive-data exposure and incomplete behavior with concrete source and caller evidence.
Review selected infrastructure configuration for concrete security, deployment and recovery risks. Cover secrets, containers, supply chain, networking, CI/CD and observability with explicit evidence gaps; do not change services or equate repository intent with live state.
Design product nudges, onboarding, reminders, habit features, and re-engagement sequences around real user goals and evidence. Produces an advisory NUDGE PLAN with copy, cadence, completion, and effective off-ramps.
Review Telegram, Discord, Slack, and other chat bot code for interaction safety, authorization, state, delivery, and resilience using the actual platform and framework contract. Read-only review with explicit coverage and unverified gates.
Review selected code changes for concrete behavioral, contract, security, and maintainability defects using the project's actual conventions. Covers generic or otherwise unclaimed review scope.
Build a concise, evidence-linked onboarding brief for an unfamiliar repository or a contributor's entry task. Maps relevant structure, flows, conventions, commands, and unknowns without changing the project.
Review comments, docstrings, TODOs, and code references for verified contradictions with surrounding behavior. Preserve meaningful rationale and operational annotations.
Review cross-cutting risks and unresolved gaps after implementation or specialist review, scaled to consequences. Return APPROVE, CONCERN, or BLOCK without manufacturing findings.
PostgreSQL specialist for evidence-backed review of query correctness and performance, schema design, indexes, transactions and migration safety in the assigned scope.
Diagnose a scoped symptom using authorized read-only logs, process, database, cache, code, and deployment evidence. Separate observed state, hypotheses, confirmed cause, and unavailable checks without executing fixes.
Review selected dependencies for verified advisories, compatibility and maintenance risk, then propose a scoped update plan. Separate outdated versions, affected packages, reachable vulnerabilities and unavailable evidence without applying upgrades.
Review selected UI components, tokens, themes, and public component APIs against the project's actual design system, approved design, and consumer contracts.
Coordinate development through 16 phases (0-15) across planning, implementation, verification, and review gates when a task needs multiple dependent steps or consequential decisions.
Review documentation freshness, accuracy, and required coverage against selected changes and actual project evidence. Distinguish confirmed drift from unavailable verification.
Expert in Drizzle ORM for TypeScript — schema design, relational queries, migrations, serverless DB integration. Use when building type-safe database layers with Drizzle, migrating from Prisma, or optimizing edge runtime DB access.
Create and execute scoped browser workflow tests with explicit real-backend or mocked-UI provenance, stable assertions, isolated data, and honest runtime/visual evidence using the project's existing runner.
Evaluate implementation behavior against explicit acceptance criteria or a Sprint Contract, separating demonstrated failure from missing evidence. Return PROCEED, ITERATE, or ESCALATE.
★not rated 3
changed todayA35 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: