菜单
Chords CI/CD workflow guidance. Use for authoring or reviewing GitHub Actions workflows under `.github/workflows`: Ubuntu/Windows builds, license-report and version-increment guards, Gradle wrapper validation, and artifact publishing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Chords build and release-engineering policy. Use for root and codegen/plugins Gradle build logic, buildSrc dependency coordinates, publishing wiring, version increments, generated `pom.xml`/`dependencies.md` reports, and the config submodule relationship.
Reviews Chords implementation changes for correctness, regressions, public API breaks, missing tests, and cross-module contract breaks. Use to review component, codegen, or build diffs. Read-only unless explicitly asked to run checks.
Chords code generation policy. Use for the ProtoData codegen plugins project, the codegen runtime library, generated MessageField/MessageOneof/MessageDef contracts, codegen correctness tests, and Protobuf declarations with Kotlin extensions in proto-values.
Chords UI component implementation policy. Use for the class-based component model, application shell, input components, layouts, message forms, validation display, dropdown/table/entity components, and server-connected components across the core, proto, and client modules.
Reviews Chords documentation changes: KDoc comments, README.md files, .agents/project.md, AGENTS.md, skills, command examples, and architecture or module maps. Read-only unless explicitly asked to run checks.
Writes, edits, and restructures Chords documentation. Use when asked to create or update README.md files, .agents/project.md, AGENTS.md, skills, KDoc comments, or inline explanatory comments. Verifies claims against current code, tests, workflows, and build files.
| name | ci-engineer |
| description | Chords CI/CD workflow guidance. Use for authoring or reviewing GitHub Actions workflows under `.github/workflows`: Ubuntu/Windows builds, license-report and version-increment guards, Gradle wrapper validation, and artifact publishing. |
Use this skill for GitHub Actions workflow work under .github/workflows/.
Publishing to Maven repositories happens automatically on master, but changes
to the publishing pipeline and its credentials remain human-reviewed; this
skill authors and reviews workflow definitions, it does not trigger them.
.github/workflows/build-on-ubuntu.yml: JDK 11 build on every push..github/workflows/build-on-windows.yml: Windows build on pull requests..github/workflows/ensure-reports-updated.yml: guard that dependencies.md
/ pom.xml (or version.gradle.kts) changed in the PR, via
config/scripts/ensure-reports-updated.sh..github/workflows/increment-guard.yml: the checkVersionIncrement guard..github/workflows/gradle-wrapper-validation.yml: wrapper JAR integrity..github/workflows/publish.yml: publishing from master, including GPG
decryption of credentials from .github/keys/.For secret handling and supply-chain safety, also use
.agents/skills/security-reviewer/SKILL.md. For the Gradle tasks the
workflows invoke, use .agents/skills/build-engineer/SKILL.md.
config submodule where scripts
from it are used.secrets.*. Never inline secret values,
tokens, or credentials into a workflow.codegen/plugins directly needs JDK 17 and runs from
codegen/plugins/.Workflows run in GitHub Actions, not locally. Verify changes by static review:
build.gradle.kts, config/scripts,
and README files.config/ submodule configure
actions/checkout with submodule initialization.State clearly in the final response that full validation happens in CI.
Follow the git-history and safety policy in AGENTS.md.