菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Install and verify Ambient Code Platform on an OpenShift cluster using quay.io images. Use when deploying Ambient to any OpenShift namespace — production, ephemeral PR test instances, or developer clusters. Covers secrets, kustomize deploy, rollout verification, and troubleshooting.
Perform any development work on the ambient-ui component. Full workflow instructions.
Deploy, update manifests, and troubleshoot the ambient-ui component. Use when creating or modifying deployment manifests, adding ambient-ui to a new overlay, building images, or debugging cluster issues.
Discover domain-specific skills and context before starting any coding or spec work. This is the mandatory first step for every task — no matter how trivial. Triggers on: any code change, spec change, implementation task, bug fix, refactor, feature work, or documentation update that touches component code or specs.
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.
| 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/