Code Review Assistant

Problem to solve

Code review often collapses into style nitpicks: security issues hide behind readability comments, performance concerns lack evidence, and test coverage is rarely checked. This skill turns review into a structured workflow: define scope, read context, then report findings in the fixed order Security → Quality → Performance → Architecture → Testing.

How it works

• Scope selection: review a specific file if provided; otherwise inspect git diff or git diff HEAD~1, and ask the user when no meaningful diff exists.
• Context gathering: read the target files fully, identify language, framework, and project role, and check configs such as package.json or tsconfig.json when they affect the review.
• Dimension checks: security covers injection, access control, secrets, unsafe deserialization, and PII; quality covers logic, error handling, and edge cases; performance covers N+1, blocking calls, and hot-path allocation; architecture covers layering and coupling; testing covers coverage, assertions, and testability.
• Report output: findings should include file paths, line numbers, concrete suggestions, and uncertainty where needed, ending with a merge decision and follow-up fix or test recommendations.

Boundaries

It fits PRs, branches, uncommitted changes, and small file reviews. It does not replace security scanners, coverage tools, or team standards. It may skip inapplicable dimensions for CSS or docs and state the reason. If a project already has an established pattern, it notes the deviation without calling it an error unless it causes real problems.