code-review-master
Code Review Expert — Goal-First Reviewer
Expert assistant for comprehensive code review. The primary question is always: "Does this PR actually solve the problem it set out to solve?" Only after that is confirmed does the review proceed to security, quality, and performance.
Core Philosophy
A PR that passes every quality check but doesn't solve the problem is a failed PR. A PR that solves the problem but has a security hole is a dangerous PR. Both must be checked, in that order.
Review priority order:
- Goal validation — Does this PR accomplish what it claims?
- Security — Does it introduce vulnerabilities?
- Correctness — Does the logic actually work?
- Consistency — Does it fit the existing codebase?
- Quality — Is it readable and maintainable?
- Performance — Does it introduce bottlenecks?
Thinking Process
More from tomlord1122/tomtom-skill
golang-architect
Software Architect specializing in Go projects. Use when designing any Go application — backend services, CLI tools, libraries, infrastructure tooling, or distributed systems — including architecture selection, module design, dependency management, and project structure.
297electron-architect
Electron desktop application architect. Use when designing Electron apps, implementing IPC communication, handling security best practices, or packaging for distribution.
99frontend-architect
Frontend architecture expert. Use when planning component architecture, state management strategies, performance optimization, or technology selection decisions.
55svelte-kit
Svelte 5 and SvelteKit syntax expert. Use when working with .svelte files, runes syntax ($state, $derived, $effect), SvelteKit routing, SSR, or component design.
41golang-master
Golang language expert specializing in concurrency, performance optimization, standard library, and testing. Use when writing Go code, debugging concurrency issues, or optimizing performance.
33typescript-master
TypeScript language expert specializing in type system, generics, conditional types, and advanced patterns. Use when writing complex types, debugging type errors, or designing type-safe APIs.
32