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

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？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

このリポジトリのすべてを見る

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.