// Use GitHub (via MCP) for Cloudbreak PRs, checks, and diffs from the editor. Pairs with cb-reviewer for standards and cb-triage/cb-junior-dev for ticket context.
Official CDP Public Cloud documentation lookup. Use this skill when any agent (Developer, Architect, Reviewer) needs to verify official Cloudera requirements, release notes, or API specifications for the Public Cloud.
Local build and test ergonomics for Cloudbreak—Gradle commands, module-scoped tests, checkstyle, and how they relate to GitHub Actions PR workflows.
Operate read-first against AWS, Azure, and optionally GCP from the terminal or cloud MCP tools—instances by region, related compute/network resources, and troubleshooting. For Cloudbreak work in cloud-aws-*, cloud-azure, cloud-gcp modules.
Senior-level thoroughness for Jira ticket resolution in the Cloudbreak project. Use this skill to fetch a Jira ticket, research related Confluence documentation, analyze the root cause, create reproduction tests, implement fixes, and prepare a high-quality PR.
Turn a Jira issue into an actionable engineering plan for Cloudbreak—without implementing code. Use this skill for fast triage, scope discovery, and verification checklists using Atlassian MCP, Confluence (CB Engineering Home), and local repo inspection.
Governance and architectural standards for the Cloudbreak project. Use this skill to understand directory structures, coding guidelines, commit message rules, and API design principles.
| name | cb-github-workflows |
| description | Use GitHub (via MCP) for Cloudbreak PRs, checks, and diffs from the editor. Pairs with cb-reviewer for standards and cb-triage/cb-junior-dev for ticket context. |
This skill describes how to wire GitHub into Cloudbreak work when a GitHub MCP server is available. Exact tool names depend on the MCP package and client; they often appear as mcp_github_* or github_*. Prefer read operations unless the user explicitly asks to create or merge.
| Goal | Approach |
|---|---|
| Find PRs for ticket CB-XXXXX | Search PRs/commits where title or branch contains CB-XXXXX; GitHub Jira linking on PRs is driven by CB-XXXXX in commit subjects (see root GEMINI.md CI section). |
| Understand CI / checks | List workflow runs or check suites for the PR’s head SHA; summarize failing jobs and log hints. |
| Review diff scope | Get the PR diff or file list; cross-check with cb-reviewer (only related files, no surprise churn). |
| Read review comments | Thread review comments and inline feedback; group by file for actionable edits. |
| Compare to base branch | Confirm PR is rebased or merged with target; cb-reviewer flags merge commits on feature branches. |
cloudbreak/cloudbreak (see .github/workflows/pull-request.yaml PROJECT env)..github/workflows/ — e.g. pull-request.yaml runs Jira update, unit tests, and other jobs on pull_request.CB-XXXXX-short-description per .gemini/WORKFLOW.md.Use whatever names your client exposes; typical operations include:
core/, datalake/, etc.).If a tool is missing, fall back to gh CLI in the terminal (read-only: gh pr view, gh pr checks) where authenticated.
cb-reviewer — Apply commit message, API, and rebase rules to what GitHub returns.cb-triage / cb-junior-dev — Correlate Jira state with PR state; paste PR URL into Jira when closing the loop per .gemini/WORKFLOW.md Phase 6.