review-pr

Automate Git merge request reviews across GitLab with commit, pipeline, and Jira checks.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dmzoneill/skills --skill review-pr-dmzoneill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/dmzoneill/skills/tree/main/review-pr
Command: npx skills add https://github.com/dmzoneill/skills --skill review-pr-dmzoneill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process for Merge Requests (MRs) or Pull Requests (PRs) by automating checks for commit format, pipeline status, Jira context, code quality, and optional local tests, leading to faster and more consistent reviews.

Core Features & Use Cases

  • Automated Context Gathering: Pulls MR details, commit history, pipeline status, and Jira issue information.
  • Code Quality Checks: Validates commit messages, description completeness, and performs security/performance analysis on code changes.
  • Optional Local Testing: Can checkout the branch and run local tests if configured.
  • Automated Actions: Can auto-approve MRs or post detailed feedback based on the review outcome.
  • Use Case: When a colleague submits a new feature branch for review, this Skill can automatically check if the commit messages follow the team's standard, if the CI pipeline passed, if the associated Jira ticket is linked, and if there are any obvious security vulnerabilities before a human reviewer even looks at it.

Quick Start

Use the review-pr skill to review merge request with ID 1234.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate pull request reviews for GitLab merge requests?

Automate GitLab merge request reviews by using a skill that gathers MR context, validates commit messages, checks CI/CD pipeline status, and performs security analysis. It provides detailed feedback or auto-approval to streamline developer workflows.

Can I automatically verify Jira ticket integration during a code review?

Verifying Jira ticket integration during automated code review is possible by pulling associated issue information alongside MR details. The skill checks if the Jira ticket is properly linked before a human reviewer evaluates the branch.

What is the best way to check CI/CD pipeline status before approving a PR?

Checking CI/CD pipeline status before PR approval is best handled by automated review tools that analyze pipeline results alongside code quality. This ensures commits pass continuous integration checks before merging.

How do I validate commit formatting and code quality in an automated workflow?

Validate commit formatting and code quality in an automated workflow by running a review process that analyzes commit history and performs security checks. This enforces consistent commit messages and code standards across merge requests.

Does automated code review work without running local tests on the branch?

Automated code review works without local tests by relying on pipeline status and static analysis, but local test execution can be optionally configured. This flexibility allows teams to balance review speed with thorough validation.