菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | build-engineer |
| description | 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. |
Use this skill for build, dependency, and release-plumbing work:
build.gradle.kts, settings.gradle.kts, version.gradle.kts, and
gradle.properties.buildSrc/ dependency coordinates, repository helpers, and convention
plugins (jvm-module, publishing, reports).codegen/plugins Gradle project's own build logic and its
codegen-workspace resource packaging.spinePublishing, artifact prefix, destination
repositories, and the publishCodegenPlugins* tasks.pom.xml / dependencies.md reports.quality/.For workflow YAML under .github/workflows, use
.agents/skills/ci-engineer/SKILL.md.
codegen/plugins uses JDK 17 / Gradle 9.4.x / Kotlin 2.3.20.
Keep build logic compatible with the owning toolchain.buildSrc/src/main/kotlin/io/spine/internal/dependency/, one object per
library, following the existing pattern. Do not inline version strings into
module build files.chordsVersion in version.gradle.kts
(2.0.0-SNAPSHOT.<N>); CI enforces this with checkVersionIncrement.pom.xml and dependencies.md are generated by the build (PomGenerator and
LicenseReporter); regenerate them via ./gradlew build rather than editing,
and include the regenerated files in version-bump changesets.config/ submodule is owned by SpineEventEngine/config; do not edit
its contents here. If shared build logic must change, describe the upstream
change instead.publish or publishCodegenPlugins against remote repositories;
publishing is CI-owned (pushes to master). Local verification uses
publishToMavenLocal.modulesWithChordsCodegen lists the
modules that get the io.spine.chords Gradle plugin, and
createCodegenWorkspace depends on publishCodegenPluginsToMavenLocal.io.spine.chords in build.gradle.kts and
Spine.kt in buildSrc) consistent in both places when bumping it.Root build (repository root, JDK 11):
./gradlew clean build
./gradlew publishToMavenLocal
./gradlew checkVersionIncrement
Codegen plugins build (from codegen/plugins/, JDK 17):
./gradlew build
./gradlew publishToMavenLocal
Run the publishToMavenLocal variant when plugin publication is part of the
change, so root modules consume the rebuilt plugins.
After version or dependency changes, confirm pom.xml and dependencies.md
were regenerated and reflect the new version.
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.
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.