gerrit
Submit, amend, and review Gerrit changes using git-review CLI. Use when asked to submit a patchset, download a change, rebase a change request, check CR status, or manage code reviews in Gerrit.
What this skill does
# Gerrit Skill This skill provides Gerrit code review integration using `git-review` with a Python wrapper for markdown-formatted query output on read/view operations. Action commands (submit, review, abandon) should use `git-review` or SSH commands directly. ## Prerequisites **Install git-review**: `pip install git-review` — [docs](https://docs.opendev.org/opendev/git-review/latest/installation.html) ## Authentication git-review uses SSH for authentication with Gerrit servers. ```bash # Configure Gerrit username (if different from local user) git config --global gitreview.username yourgerrituser # Test SSH connection ssh -p 29418 [email protected] gerrit version # Add SSH key to Gerrit # 1. Generate SSH key if needed: ssh-keygen -t ed25519 # 2. Copy public key: cat ~/.ssh/id_ed25519.pub # 3. Add to Gerrit: Settings > SSH Keys ``` Gerrit supports multiple authentication methods: - **SSH** (recommended): Used by git-review for all operations - **HTTP/HTTPS**: For web UI and REST API access (set password in Settings > HTTP Password) See [Gerrit Authentication](https://gerrit-review.googlesource.com/Documentation/user-upload.html#ssh) for details. ## Initial Setup ### Configure Repository ```bash # One-time setup for a repository git review -s # Or manually create .gitreview file in repository root cat > .gitreview <<EOF [gerrit] host=review.example.com port=29418 project=myproject defaultbranch=main EOF ``` See [Installation Guide](https://docs.opendev.org/opendev/git-review/latest/installation.html) for details. ## Script Usage The wrapper script (`scripts/gerrit.py`) uses Gerrit SSH query commands and formats output as markdown. Connection details are read from `.gitreview` or provided via `--host`/`--port`/`--username` flags. See [permissions.md](references/permissions.md) for read/write classification of each command. ```bash # Check Gerrit SSH access $SKILL_DIR/scripts/gerrit.py check # Changes $SKILL_DIR/scripts/gerrit.py changes list $SKILL_DIR/scripts/gerrit.py changes view 12345 $SKILL_DIR/scripts/gerrit.py changes search "status:open project:myproject" # Projects $SKILL_DIR/scripts/gerrit.py projects list ``` All commands support `--limit N` for list commands (default 30). Global connection options: `--host`, `--port` (default 29418), `--username`. ## Commands (Direct git-review Usage) For action commands, use `git-review` or SSH commands directly: ### Submitting Changes ```bash git review # Submit current branch for review git review -t topic-name # Submit with topic git review -f # Submit and close local branch git review --reviewers user1,user2 # Add reviewers git review -n # Dry-run (show what would be done) ``` Full reference: [git-review usage](https://docs.opendev.org/opendev/git-review/latest/usage.html) ### Downloading Changes ```bash git review -d 12345 # Download change 12345 git review -d 12345,3 # Download patchset 3 of change 12345 git review -x 12345 # Cherry-pick change (no branch) git review -m 12345 # Compare local changes to remote ``` Downloads create a local branch named `review/username/topic`. ### Updating Changes ```bash # Make changes to downloaded review git commit --amend git review # Upload new patchset # Update to latest patchset git review -d 12345 # Re-download updates the branch ``` ### Advanced Options ```bash git review -R # Don't rebase (submit as-is) git review -D # Draft mode (WIP changes) git review --no-cache # Skip local cache git review -v # Verbose output git review --track # Track remote branch ``` ## Configuration ### Per-Repository Settings File: `.gitreview` (repository root) ```ini [gerrit] host=review.example.com port=29418 project=myproject/subproject defaultbranch=main defaultremote=origin ``` ### Global Settings ```bash # Set Gerrit username git config --global gitreview.username myuser # Set default remote git config --global gitreview.remote gerrit # Configure scheme (ssh/http/https) git config --global gitreview.scheme ssh ``` Configuration stored in `~/.gitconfig` ## Examples ### Daily Workflow ```bash # Start work on new feature git checkout -b feature-branch # ... make changes ... git commit -m "Add new feature" # Submit for review git review -t feature-topic # Verify submission $SKILL_DIR/scripts/gerrit.py changes list # confirm change appears # Address review comments # ... make changes ... git commit --amend git review # Verify new patchset uploaded $SKILL_DIR/scripts/gerrit.py changes view <change-number> ``` ### Reviewing Others' Changes ```bash # Download change for review git review -d 12345 # Verify download $SKILL_DIR/scripts/gerrit.py changes view 12345 # Test the change # ... run tests, verify code ... # Return to main branch git checkout main git branch -D review/user/topic ``` ### Working with Topics ```bash # Submit with topic git review -t authentication-refactor # Verify submission $SKILL_DIR/scripts/gerrit.py changes list # All related changes will be grouped under this topic git commit -m "Part 2: Update tests" git review -t authentication-refactor ``` See [common-workflows.md](references/common-workflows.md) for more examples. ## Advanced Usage See [advanced-usage.md](references/advanced-usage.md) for SSH commands, JSON output, and multi-server configuration. ## Model Guidance This skill wraps an official CLI. A fast, lightweight model is sufficient. ## Troubleshooting See [troubleshooting.md](references/troubleshooting.md) for common issues and fixes. ## Official Documentation - **git-review Manual**: <https://docs.opendev.org/opendev/git-review/latest/> - **git-review Repository**: <https://opendev.org/opendev/git-review> - **Gerrit Documentation**: <https://gerrit-review.googlesource.com/Documentation/> - **Gerrit SSH Commands**: <https://gerrit-review.googlesource.com/Documentation/cmd-index.html>
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.