Agent Skills
› midudev/autoskills
› android-gradle-build-logic
android-gradle-build-logic
GitHub用于规范 Android Gradle 构建逻辑，涵盖版本目录、插件及约定模式。通过最小化变更提升构建正确性与可维护性，确保工具链兼容并遵循官方最佳实践。
Trigger Scenarios
Android Gradle 插件配置与设置
修复 Android 模块的构建逻辑问题
为 Android 仓库配置版本目录
Install
npx skills add midudev/autoskills --skill android-gradle-build-logic -g -y
SKILL.md
Frontmatter
{
"name": "android-gradle-build-logic",
"metadata": {
"tags": [
"android",
"gradle",
"build",
"toolchain"
],
"owners": [
"@android-agent-skills\/maintainers"
],
"version": "0.1.0",
"category": "foundations",
"triggers": {
"exclude": [
"room schema migration only",
"compose layout only",
"notification permission flow"
],
"include": [
"android gradle plugin setup",
"fix build logic for android modules",
"version catalog for android repo",
"gradle convention cleanup for android",
"agp build logic change"
]
},
"test_targets": [
"examples\/orbittasks-compose",
"examples\/orbittasks-xml",
"benchmarks\/triggers.jsonl"
]
},
"description": "Shape Android build logic with Gradle, version catalogs, plugins, convention patterns, and toolchain compatibility."
}
Android Gradle Build Logic
When To Use
- Use this skill when the request is about: android gradle plugin setup, fix build logic for android modules, version catalog for android repo.
- Primary outcome: Shape Android build logic with Gradle, version catalogs, plugins, convention patterns, and toolchain compatibility.
- Handoff skills when the scope expands:
android-modernization-upgradeandroid-ci-cd-release-playstore
Workflow
- Map the request to the current Android stack, module boundaries, and minimum supported API level.
- Inspect the existing implementation for implicit assumptions, duplicate helpers, and outdated patterns.
- Apply the smallest change that improves correctness, readability, and long-term maintainability.
- Validate the result against the relevant showcase app path and repo benchmarks.
- Hand off adjacent work to the next specialized skill only after the core foundation is stable.
Guardrails
- Prefer official Android and Kotlin guidance over custom local conventions when they conflict.
- Keep public APIs boring and explicit; avoid clever abstractions that hide Android lifecycle costs.
- Do not mix architectural cleanup with product behavior changes unless the request explicitly needs both.
- Document any compatibility constraints that will affect old modules or generated code.
Anti-Patterns
- Sprinkling helpers across modules without a clear ownership boundary.
- Introducing framework-specific code into pure domain or data layers.
- Refactoring every adjacent file when only one contract needed to change.
- Leaving migration notes implied instead of writing them down.
Examples
Happy path
- Scenario: Run the Compose showcase build from a clean checkout with version catalogs.
- Command:
cd examples/orbittasks-compose && ./gradlew :app:assembleDebug
Edge case
- Scenario: Validate shared repositories and plugin management in the XML fixture.
- Command:
cd examples/orbittasks-xml && ./gradlew :app:assembleDebug
Failure recovery
- Scenario: Benchmark build-logic trigger precision against modernization and CI skills.
- Command:
python3 scripts/eval_triggers.py --skill android-gradle-build-logic
Done Checklist
- The implementation path is explicit, minimal, and tied to the right Android surface.
- Relevant example commands and benchmark prompts have been exercised or updated.
- Handoffs to adjacent skills are documented when the request crosses boundaries.
- Official references cover the chosen pattern and the main migration or troubleshooting path.
Official References
Version History
- 0ec7253 Current 2026-07-24 20:51
