// Use when creating or updating Gerrit changes — pushing code for review, amending patch sets, setting reviewers and topics. Triggers on "push to Gerrit", "create a Gerrit change", "upload for review", "update the patch set", "add reviewers to this change".
Perform any development work on the ambient-ui component. Full workflow instructions.
Deploy a PR's images (api-server, control-plane, runner) to any OpenShift namespace for integration testing. Works on both standard OpenShift clusters and MPP managed clusters. Auto-detects the environment and chooses the right script.
End-to-end development workflow for the Ambient Code Platform. Covers ticket → branch → spec → code → commit → PR → review → deploy → verify. Self-improving: update this skill whenever a failure path is discovered or a shortcut is validated. Git history is the audit trail.
Required context for all frontend work. Loads frontend standards (conventions, React Query patterns, adapter testing requirements) before any code changes. Use when modifying anything under components/frontend/. Triggers on: any frontend code change, UI component work, React Query hooks, API adapter work, frontend bug fix, frontend refactor.
Use when reviewing a Gerrit change — fetching change details, reading diffs, posting inline comments, and voting with labels. Triggers on "review this Gerrit change", "review change 12345", "look at this Gerrit CL", "code review on Gerrit".
Use when submitting or preparing a Gerrit change for merge — checking submit requirements, rebasing, resolving comments, and submitting. Triggers on "submit this Gerrit change", "merge this CL", "is this change ready to submit", "check submit requirements".
| name | gerrit-create |
| description | Use when creating or updating Gerrit changes — pushing code for review, amending patch sets, setting reviewers and topics. Triggers on "push to Gerrit", "create a Gerrit change", "upload for review", "update the patch set", "add reviewers to this change". |
Guide for pushing code changes to Gerrit for review.
The Gerrit MCP server must be available and git must be configured with the appropriate remote.
Gerrit changes are created by pushing commits to a special ref:
git push origin HEAD:refs/for/<target-branch>
Commit message format: Gerrit requires a Change-Id footer in the commit message. If the Gerrit commit-msg hook is installed, it adds this automatically. If not:
Subject line (50 chars max)
Body explaining what and why (wrapped at 72 chars).
Change-Id: I<40-char-hex>
Single commit per change: Each commit becomes one Gerrit change. Squash work-in-progress commits before pushing.
Target branch: Usually main or master, but verify the project's default branch.
Add metadata via push options:
git push origin HEAD:refs/for/main \
-o topic=my-feature \
-o r=reviewer@example.com \
-o cc=watcher@example.com \
-o wip
topic=<name> — group related changesr=<email> — add reviewercc=<email> — add CCwip — mark as work-in-progressready — mark as ready for reviewhashtag=<tag> — add hashtagTo upload a new patch set for an existing change:
Amend the commit (keep the same Change-Id):
git commit --amend
Push again:
git push origin HEAD:refs/for/main
Gerrit matches the Change-Id to the existing change and creates a new patch set.
After a change exists, use mcp__gerrit__submit_gerrit_review to:
Use mcp__gerrit__fetch_gerrit_change to verify the change was created/updated correctly.
gitdir=$(git rev-parse --git-dir); scp -p -P 29418 <user>@<host>:hooks/commit-msg ${gitdir}/hooks/