Code Review Assistant

Problem

Code review often stops at formatting and obvious bugs, without a consistent check for intent, context, tests, and security. This skill turns review into a repeatable workflow: identify whether the target is local uncommitted changes or a remote PR/MR, collect the necessary diff and verification context, then produce structured feedback.

How it works

• Review target: if a PR number or URL is provided, review that remote PR; if the user asks to review changes, inspect git status, git diff, and git diff --staged.
• Context preparation: for remote GitLab MRs, request the MR description, goal, and diff when API access is restricted; if the codebase is available locally, run verification such as npm run preflight.
• Analysis: evaluate Correctness, Maintainability, Readability, Efficiency, Security, Edge Cases and Error Handling, and Testability.
• Feedback: produce a Summary, Critical findings, Improvements, optional Nitpicks, and a Conclusion with Approved or Request Changes.
• Cleanup: after remote PR review, ask whether to switch back to main or master.

Boundaries

It works best when the change, project description, and verification command are available. With missing MR goals, diffs, or local verification output, the review should be treated as conservative. It does not replace full test execution, architecture review, or org-level compliance checks.