gitlab-ci-review

Review GitLab CI integration scripts, jq filters, and merge request comment formatting.

4.4k|154|Updated Mar 17, 2026

Search Tags:#pipeline #jq #merge request #shell scripts #GitLab #ci #Code review

One-click install

npx skills add https://github.com/fallow-rs/fallow --skill gitlab-ci-review

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-ci-review
Source: https://github.com/fallow-rs/fallow/tree/main/.agents/skills/gitlab-ci-review
Command: npx skills add https://github.com/fallow-rs/fallow --skill gitlab-ci-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changes to GitLab CI pipelines, shell scripts, and jq filters are easy to break in subtle ways, such as quoting bugs or malformed MR comments. This Skill provides a structured review checklist so reviewers consistently verify CI behavior before approving changes.

Core Features & Use Cases

Guided CI Review: Directs the reviewer to read the dedicated GitLab CI reviewer agent instructions before evaluating changes.
Test and Formatting Checks: Ensures relevant tests in ci/tests/ and shell/jq quoting and formatting behavior are examined.
Standardized Verdicts: Ends every review with a clear APPROVE, CONCERN, or BLOCK outcome.
Use Case: When a pull request modifies files under ci/ or changes GitLab-specific report output, invoke this Skill to run a consistent review of scripts, jq filters, and MR comment rendering.

Quick Start

Review the current changes to the ci/ directory and GitLab MR comment formatting, then give an APPROVE, CONCERN, or BLOCK verdict.

Frequently Asked Questions about gitlab-ci-review

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

FAQPage Schema

How do I review GitLab CI pipeline changes in a pull request?▼

Read the dedicated reviewer instructions, then examine the changed shell scripts, jq filters, and MR comment formatting alongside the tests in ci/tests/. Finish with a clear APPROVE, CONCERN, or BLOCK verdict.

What should I check when reviewing jq filters in CI scripts?▼

Check quoting and escaping behavior in the jq filters and surrounding shell scripts, since subtle quoting bugs can corrupt report output. Verify the relevant tests in ci/tests/ cover the changed behavior.

When should this GitLab CI review process be used?▼

Use it whenever changes touch the ci/ directory or alter GitLab-specific output behavior such as MR comments and report formatting. It is not intended for general application code reviews.

What review outcomes does the GitLab CI review produce?▼

Every review ends with one of three standardized verdicts: APPROVE when changes are safe, CONCERN when issues need discussion, or BLOCK when changes must not merge.