菜单
Update gradle/libs.versions.toml toward latest stable and verify safely. Triggered by "dependency-bump", "/dependency-bump", "update dependencies", "bump versions". Follows the dependency checklist in docs/tech/findings.md.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Write or extend tests for the Chai repo. Triggered by "write a test", "add tests", "test this", or as the follow-up when a component/util lands without coverage. Local unit tests use JUnit 6 (Jupiter); Compose/UI behaviour is tested as instrumented tests. Picks the right source set and idioms; does not invent mocking/assertion libraries the catalog does not declare.
Find design-system violations in Chai source — raw Material components, hardcoded colors, bare .dp magic numbers, @Preview instead of @ChaiPreview. Triggered by "audit-design-system-usage", "/audit", or by checks/code-reviewer. This is the check the broken chailinter is meant to do. Reports; does not edit.
Verify the Chai project assembles. Triggered by "check-build", "/check-build", "does it build", or by checks as the assemble gate. Runs `./gradlew assembleDebug` only — no mutation, no formatting.
Run Android Lint on Chai and report. Triggered by "check-lint", "/check-lint", "run lint", or by checks as the lint gate. Runs `./gradlew lintDebug` only — reports the first violation, never edits.
Umbrella pre-PR gate for Chai. Triggered by "checks", "/checks", "run the checks", or by any agent that needs a green light before committing or opening a PR. Runs the design-system audit, Android Lint, unit tests, and a debug assemble, then reports a single pass/fail.
Produce a commit subject, branch name, and PR title that match Chai's conventions. Triggered by "commit-convention", "/commit-convention", "write a commit message", or by the gitter agent before committing or opening a PR.
| name | dependency-bump |
| description | Update gradle/libs.versions.toml toward latest stable and verify safely. Triggered by "dependency-bump", "/dependency-bump", "update dependencies", "bump versions". Follows the dependency checklist in docs/tech/findings.md. |
You move the version catalog toward latest stable and prove the build still works. Catalog is the single source of truth: gradle/libs.versions.toml. Edit versions there, never pin in module build.gradle.kts.
./gradlew dependencyUpdates # if the Ben Manes plugin is present; else inspect the catalog by hand
Cover the whole catalog, not just the toolchain: agp, kotlin, composeBom, lint/lintTests, coreKtx, appcompat, material, material3/material3Android, lifecycle, activity-compose, the Compose runtime/ui-tooling pins, and the test stack (androidx.test.ext:junit, espressoCore).
runtimeAndroid / uiTooling / material3Android pins. Several pins exist only because the BOM isn't relied on consistently.kotlin and the compose-compiler plugin in lockstep (same kotlin ref).composeOptions { kotlinCompilerExtensionVersion = … } in module build files — it does nothing under Kotlin 2.x../gradlew clean lintDebug testDebugUnitTest assembleDebug --configuration-cache
Read the release notes for any major bump (AGP, Kotlin, Compose) and check known deprecations in findings.md (e.g. statusBarColor on API 35, manifest package attribute).
Treat the bump as its own change, on a fix/… or chore-style feature/deps-… branch off develop. Atomic: the catalog change in one commit (Updated dependencies to latest versions); any code fixes for breaking changes in follow-up commits. Per commit-convention. Do not bundle unrelated work.
A version bump that doesn't build is worse than none. If verification fails and the fix isn't small, stop and report which dependency broke rather than chasing a cascade.