motoedie/motoedie-code-review
Code review skills: change analysis, behavior, quality, security, SQL health, and test gaps.
Report-only project-impact summary of current branch changes. Explains the problem the change answers, what changed, and its direct and downstream effects on system behavior, UX, workflows, contracts, compatibility, and operations. Use before opening an MR or when a reviewer needs concise project context. Does not perform defect, maintainability, or security review.
Report-only review of changed code for functional correctness, data and API contracts, and performance and resource risks. Use for branch, staged, uncommitted, or path-scoped defect review. Excludes test-gap, structural maintainability, lint, type-checker, and security analysis.
Report-only review of changed production code for structural maintainability after implementation, especially after reactive edits. Checks minimal change, single responsibility and misleading names, duplication, coupling, and module boundaries. Richard Ejem adds clarity/contracts, type modeling, reuse/evolution, and nit findings. Excludes lint/typechecker and test concerns. Supports base, path, revision-range, uncommitted, focus/skip, and instruction scopes.
Report-only security analysis of code changes and selected paths for vulnerabilities and security test gaps. Reviews untrusted input, auth, sessions, APIs, files, network calls, commands, queries, parsing, secrets, and dependencies. Supports uncommitted, staged, branch, base-ref, revision-range, and path scopes; quick, standard, deep, and focus options.
Report-only review of SQL queries affected by code changes, using PostgreSQL schema and index metadata plus EXPLAIN to find injection, query-plan, performance, and index problems. Also reviews changed migrations when they affect reviewed queries or schema. Supports local Git scopes. Excludes general database operations, transaction or locking analysis, PostgreSQL tuning, and unrelated migration safety.
Report-only review of changed code for meaningful behavior-focused test gaps. Use for branch, staged, uncommitted, path-scoped, or GitLab merge-request CI review. Does not write tests, find general code defects, or review security-specific test gaps.