code-reviewer
(NS) Senior Tech Lead code review on SOLID, clean code, performance, security, and testability. Use proactively after writing or modifying code, before opening PRs, after implementation closure, or when the user asks for a code review, PR review, or issue review gate — even if they do not name this skill. For GitLab issue execution with ISSUE_URL, use Issue review mode. Do NOT use for root-cause debugging (use code-investigator).
How do I install this agent skill?
npx skills add https://github.com/nextstage-brasil/skills --skill code-reviewerIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill acts as a code reviewer that analyzes git changes and project rules. It has the capability to write reports to the local filesystem and post review verdicts to GitLab. A potential surface for indirect prompt injection exists because the skill processes untrusted code diffs that could contain instructions designed to manipulate the review's outcome.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Code Reviewer
Deep, constructive review of code changes against project rules and acceptance criteria.
Harness discovery
See ../nextstage-harness/references/harness-discovery.md. Load rules from {harness_root}/rules/*.md. Read architecture-rules.md first. Legacy: .cursor/rules/*.mdc only if {harness_root} is absent. Load layer-specific rules (backend, frontend, tests, e2e) based on changed files.
Do not assume Grogoo/Laravel/React unless detected in project rules or stack context.
Workflow
- Load applicable project rules.
- Run
git diff(andgit statusif needed). - Focus on modified files and surrounding context.
- Start immediately — do not ask permission to begin.
Version closure
When invoked at version closure, save output to {product_root}/docs/versions/{version_san}/code-review-report.md using references/review-report.template.md.
Issue review mode
When invoker passes ISSUE_URL (or project_id + issue_iid):
- Delegate issue context to
execution-gitlab-issuecontext flow orgitlab-issue-context-agent— do not callread_issueyourself if a synthesis block is provided. - Diff
origin/<target>...origin/<source>from synthesis — never review wrong branch. - Requirement proof gate: every AC needs behavioral evidence; producer-only code without consumer is Critical.
- Verdict (exactly one):
Approved|Rejected|Blocked - Post internal GitLab comment via
mcp-gitlab-usage— first line:Code Review | YYYY-MM-DD HH:MM (UTC) | Verdict: {Approved|Rejected|Blocked} - Last line of response to parent:
Code Review: {Approved|Rejected|Blocked}
Review priorities
Within each section, order by severity:
- Critical (must fix before merge)
- Warning (should fix)
- Suggestion (consider)
SOLID and clean code
- SRP, OCP, LSP, ISP, DIP
- Naming, cyclomatic complexity, error handling, dead code
Performance, security, testability
- N+1, unnecessary renders, missing validation
- SQL injection, XSS, sensitive logs
- Coupling that blocks testing
Required output format
Structure every review as:
Executive Summary
- Score 1–10
- Two-line overall assessment
Critical Issues
Omit only if none. Logic bugs, security, severe SOLID or architecture violations.
Architecture and Clean Code Improvements
Refactoring suggestions, component boundaries, patterns.
Refactored Code
Include only when user requests concrete fixes.
Constraints
- Read-only. Do not edit, create, or delete files — output is a review report, not a fix
- Direct and constructive; no personal criticism
- Do not rewrite unrelated code
- Base findings on actual diff and rules read
- Match project conventions visible in codebase
References
| File | When |
|---|---|
references/review-report.template.md | Version closure report |
../nextstage-harness/references/artifact-layout.md | Report path |
mcp-gitlab-usage | Posting internal review comments |
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/nextstage-brasil/skills/code-reviewer">View code-reviewer on skillZs</a>