mcpField
G
gerrit

gerrit

github.com/checkmkTesting & quality2.6k43 installsUpdated today
Repository

About gerrit

A Gerrit workflow skill for reviewing, validating, and submitting changes. It guides agents through change status checks, CI failure investigation, validation retriggers, and sequential submission of commit chains.

Key features

  1. 01Submit a Gerrit change and its parents
  2. 02Inspect change status and open changes
  3. 03Investigate failed validation jobs
  4. 04Retrigger change validation
  5. 05Guide sequential commit-chain submission

Use cases

  1. 01Submitting an approved Gerrit change
  2. 02Finding open changes that need attention
  3. 03Diagnosing a failed change validation
  4. 04Submitting a series of dependent commits

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/checkmk/checkmk --skill gerrit

After installing, type/gerritin Claude Code to confirm it loaded.

Details

From the project README

When asked to submit a Gerrit change:

curl -s --netrc "https://review.lan.tribe29.com/a/changes/125896/submit" -X POST -H "Content-Type: application/json" -d '{}'

This will submit the change and all its unmerged parents (provided all the changes have the required approvals).

When asked to improve a Gerrit change:

  1. Fetch the current state from Gerrit

gerrit-change-log HEAD

  1. In case a Verified -1 is reported, fetch the Jenkins job results using the jenkins skill
  2. For each failed stage, fetch the details of the triggered stage job

When asked for the list of open Gerrit changes

# List all your open changes
gerrit-change-log --list

# Find changes needing attention (negative score)
gerrit-change-log --list | grep ':-'

To retrigger the change validation

You can retrigger the change validation without pushing the commit again. If you are sure that the CV failed due to reasons outside of your change, you may retrigger the CV by posting "start: test-gerrit" on the change.

When asked to submit a commit chain

Do an rebase on top of the base branch. Select the first change and push it for review. Wait for the CV job to finish. In case it fails, gather the state from the jenkins job. Reproduce the issue locally, fix it, verify it locally, then push for review again. Do this until the CV job finishes successfully. Then follow the same procedure with the next change. Do this until all changes are verified by the CV job. At the end provide a list of changes and a summary of the necessary changes that each commit needed.

In case the command gerrit-change-log is missing

Ask the user to clone the zeug_cmk git repository and add it to their PATH. See also: https://wiki.lan.checkmk.net/x/4zBSCQ

Comments

Markdown supported