一键导入
cb-architect
// Governance and architectural standards for the Cloudbreak project. Use this skill to understand directory structures, coding guidelines, commit message rules, and API design principles.
// Governance and architectural standards for the Cloudbreak project. Use this skill to understand directory structures, coding guidelines, commit message rules, and API design principles.
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.
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.
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.
| name | cb-architect |
| description | Governance and architectural standards for the Cloudbreak project. Use this skill to understand directory structures, coding guidelines, commit message rules, and API design principles. |
This skill encodes the foundational mandates and architectural standards for the Cloudbreak project.
core, datalake, environment, freeipa, redbeams, autoscale.cloud-api, cloud-aws-*, cloud-azure, cloud-gcp.common, common-model, service-common, grpc-common..github/.application.yml files (e.g., core/src/main/resources/application.yml).String instead of Enum on the API layer for better compatibility.jakarta.* instead of javax.* (Project is on Spring Boot 3).boolean over Boolean. If Boolean is used, provide a default value.@Schema(requiredMode = Schema.RequiredMode.REQUIRED).@RequestBody(required = true) for POST, PUT, DELETE.cbd migrate ...).java.*javax.*jakarta.*org.*com.*CB-12345). Capitalize the subject after the ticket number.[service]/src/main/resources/schema.cbd migrate [db] new "Ticket-ID description".When resolving Jira tickets autonomously or with human assistance using the cb-junior-dev persona, the following additional standards apply:
Every PR must include a "Verification Steps" section in the description, listing:
./gradlew :module:test --tests ...).PRs should briefly address the impact on:
String over Enum).Flow, confirm that the state machine transitions were audited for leaks or deadlocks.Assign reviewers based on the CODEOWNERS file in the project root. Identify the target domain using the Team field (customfield_10001) (e.g., Raven Clan). For JQL against Team or resolving Atlassian team ids, see cb-jira (.agent/skills/cb-jira/SKILL.md). If the change spans multiple domains (e.g., Core and Datalake), ensure at least one reviewer from each domain is requested.