Gerritaction

What This Skill Does

The Gerritaction skill for OpenClaw is a powerful integration tool designed to interface directly with Gerrit code review systems. It allows users to bridge the gap between AI-driven natural language commands and the complex Gerrit API. By acting as a specialized worker, it enables programmatic querying of Gerrit entities such as accounts, changes, groups, and projects. Beyond simple information retrieval, the skill provides a mechanism to perform state-changing operations on code reviews, including modifying reviewer lists, managing the attention set, approving pull requests, submitting code, or even deleting changes. This allows teams to automate their CI/CD workflows, manage code review queues, and maintain Gerrit health without manual interface interaction.

Installation

To utilize this skill, first ensure your system has Python and pip installed. The skill is packaged as an independent CLI utility. You can install it via the OpenClaw registry or directly via pip:

1. Install the CLI: pip install gerritaction
2. Integrate into OpenClaw: clawhub install openclaw/skills/skills/craftslab/gerritaction
3. Configure: Edit skill/config.yml with your Gerrit host URL, port, and authentication credentials (user/pass).

Use Cases

This skill is perfect for DevOps engineers and software architects looking to streamline their development lifecycle. Common use cases include:

• Auditing pending changes: Automatically querying open changes to identify stalled code reviews.
• Reviewer Management: Adding subject matter experts to specific changes as reviewers based on file path patterns.
• Attention Management: Moving items into the 'attention set' for developers who have pending tasks.
• Automated Housekeeping: Cleaning up outdated or abandoned changes in a project.
• Group Discovery: Syncing permissions or checking member lists within Gerrit groups.

Example Prompts

1. "Find all open changes created since January 1st, 2024, that are currently assigned to the team."
2. "Add developer 'j.doe' as a reviewer to all changes currently in the 'frontend-ui' project that haven't been approved yet."
3. "Approve change 12345 with Code-Review+2 and then submit it to the repository."

Tips & Limitations

• Safety: Always ensure your Gerrit credentials are kept in a secure configuration file and not hardcoded into scripts.
• Atomicity: While you can chain actions, consider that Gerrit API operations are sequential; if one action in a sequence fails, investigate the log outputs immediately.
• Querying: Always be as specific as possible with your query strings to minimize the return set and improve performance.
• File I/O: Use the --output-file parameter when dealing with large data sets to avoid flooding your terminal output and to store results for future analysis.