ha-android-committing

Home Assistant Android change finalization. Use when finishing a change, preparing to commit, updating the changelog, naming a branch, or opening a pull request.

跳到安装

仓库: home-assistant/android
最近来源活动: 2026年8月26日 16:10
检测到的 SKILL.md 语言: 英语
星标: 3,842
分支: 1,047

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/home-assistant/android --skill ha-android-committing

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

ha-android-testing

Home Assistant Android testing guidance. Use when writing or reviewing unit tests, Robolectric tests, Flow tests with Turbine, screenshot tests, fakes from testing-unit, or module-wide test rules.

2026-07-22

ha-android-architecture

Home Assistant Android module and layer architecture. Use when adding features, choosing where code lives, writing repositories or use cases, setting up Hilt injection, storing data securely, or calling Home Assistant APIs.

2026-07-13

ha-android-concurrency

Home Assistant Android coroutine and threading guidance. Use when launching coroutines, choosing dispatchers, sharing mutable state across threads, exposing Flows, or reviewing for blocking calls and race conditions.

2026-07-13

查看这个仓库的全部 Skills

HA Android Committing

Use this skill when finalizing a change and preparing it for commit or a pull request. For evaluating the code itself, use the ha-android-review skill.

Before Committing

Format: ./gradlew :build-logic:convention:ktlintFormat ktlintFormat

Tests: ./gradlew test

If the change adds a feature or changes behavior visibly for end users, add it to app/src/main/kotlin/io/homeassistant/companion/android/changelog/ChangelogContent.kt. Small bug fixes don't get their own entry — the standing "Bug fixes and dependency updates" entry already covers them.

After adding or updating any dependency (in gradle/libs.versions.toml or module declarations), run ./gradlew alldependencies --write-locks.

Run the ha-android-review skill over the diff before handing it off.

Branch naming: feature/add-dark-mode, fix/crash-on-rotation.

Pull Requests

Use .github/pull_request_template.md as the PR body.

Keep PRs small — easier to review, faster to merge. Break large changes into logical chunks; a reusable component (a new HA* composable, a shared utility) deserves its own PR before the feature that uses it.

A PR must not contain changes unrelated to its purpose. Found a bug on the way? Open an issue and a separate PR. Revert incidental edits to files the change doesn't need.

Pure refactor or code-move PRs must not change behavior — keep copied code as it was and fix pre-existing issues in follow-ups.

Once a PR is open, merge main into the branch instead of rebasing.

Keep the PR description and screenshots up to date as the implementation evolves.

Tests belong in the same PR as the implementation they cover, including tests moved along with moved logic.

Features visible in :app must be verified on (or hidden from) Automotive and other form factors like Meta Quest.

When the Android Gradle Plugin is updated, refresh the lint baseline with ./gradlew updateLintBaseline. Never grow the baseline to silence an issue introduced by your change — fix the source or delete the unused resource instead.