Verified:GitHub

code-review

Review GitLab Merge Requests for code quality and maintainability issues.

Updated May 18, 2021

Search Tags:#linting #review #code-quality #gitlab #code-review #merge-request

One-click install

npx skills add https://github.com/jwbaldwin/dotfiles --skill code-review-jwbaldwin

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/jwbaldwin/dotfiles/tree/main/.config/opencode/skills/code-review
Command: npx skills add https://github.com/jwbaldwin/dotfiles --skill code-review-jwbaldwin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps perform a thorough review of a GitLab Merge Request, focusing on code quality, maintainability, and practical engineering patterns before merging.

Core Features & Use Cases

Quality-focused review: Analyze MR for readability, maintainability, and adherence to codebase conventions.
Pattern spotting: Identify token-inefficient patterns, unnecessary verbosity, and missing abstractions.
Documentation & tests: Highlight gaps in tests or documentation and suggest improvements.
Use Case: Before merging, run this skill to surface potential issues and propose concrete improvements.

Quick Start

Provide a LINK_TO_GITLAB_MR, BRANCH-NAME, or TICKET-ID to fetch MR details via Zapier MCP, then perform a structured review highlighting risks, suggested refactors, and test coverage gaps.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review a GitLab merge request for code quality?▼

GitLab merge request reviews assess code quality by evaluating readability, maintainability, adherence to conventions, DRY/SOLID principles, error handling, test coverage, and performance implications. Provide a GitLab MR link, branch name, or Jira ticket ID to fetch details and receive structured findings with actionable refactor suggestions.

Can I automate code review checks before merging in GitLab?▼

Yes. Automated code review identifies token-inefficient patterns, unnecessary verbosity, missing abstractions, test gaps, and documentation deficiencies. Run the review on your MR to surface risks and integration readiness issues before merging, reducing manual review overhead.

What does a code quality review check for?▼

Code quality reviews examine readability, maintainability, DRY and SOLID adherence, error handling and logging practices, test coverage, performance implications, and conformance to project conventions. Results highlight risks, suggest concrete refactors, and identify missing tests or documentation.

Does this work with GitLab merge requests and Jira tickets?▼

Yes. The review tool accepts GitLab MR links, branch names, or Jira ticket IDs. It fetches MR details via Zapier MCP integration, then performs quality assessment and outputs findings regardless of input format.

What's the best way to catch code quality issues early in development?▼

Run a structured code review on your GitLab MR before merging. This process identifies maintainability gaps, pattern inefficiencies, test coverage shortfalls, and integration risks upfront, preventing technical debt and ensuring adherence to project standards.