build-system-expert

Diagnose Android build failures from Soong and Kati rule issues.

40|7|Updated Mar 14, 2026

Search Tags:#dependency-resolution #vndk #android-build #soong #kati #android.bp #partition-images

Ready to run

npx skills add https://github.com/jonaschen/Android-Software --skill build-system-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-system-expert
Source: https://github.com/jonaschen/Android-Software/tree/main/skills/L2-build-system-expert
Command: npx skills add https://github.com/jonaschen/Android-Software --skill build-system-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill prevents hallucinated build paths and partition errors by grounding Android.bp and Android.mk troubleshooting in Soong/Kati conventions whenever ninja or m commands fail.

Core Features & Use Cases

Soong and Kati diagnostics: Verify module definitions, visibility, enabled flags, and dependency chains across all build directories.
Partition and VNDK guidance: Clarify how system/vendor/product/odm boundaries and VNDK rules affect module placement and linking decisions.
Use Case: When a depends on disabled module or duplicate module error appears, explain which Android.bp file, flag, or boundary needs adjustment and reference the canonical build/make/core/main.mk logic.

Quick Start

Ask the build-system-expert to inspect the latest ninja failure and highlight the Android.bp dependency rules that caused it.

Frequently Asked Questions about build-system-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix Android.bp dependency errors during the Android 15 build?▼

To fix Android.bp dependency errors, verify module definitions, visibility, and enabled flags across build directories. Check for disabled module dependencies and duplicate module errors, referencing canonical build/make/core/main.mk logic to adjust boundaries.

What causes duplicate module errors in Soong and Kati?▼

Duplicate module errors in Soong and Kati occur when multiple Android.bp or Android.mk files define the same module name. Resolve this by locating the conflicting definitions and adjusting the module visibility or enabled flags.

How do VNDK boundaries affect system and vendor partition image assembly?▼

VNDK boundaries dictate module placement and linking between system, vendor, product, and odm partitions. Correctly configuring VNDK rules ensures modules are placed on the appropriate partition image without violating build system restrictions.

How do I diagnose ninja build failures caused by Kati rule issues?▼

Diagnose ninja build failures from Kati rule issues by inspecting Android.mk edits and tracing dependency chains. Ensure your troubleshooting respects Android 15 build system restrictions and prebuilts workflow conventions.

Does this build system guidance cover toolchain and bionic workflows?▼

Yes, the build system guidance covers toolchain and bionic workflows. It grounds troubleshooting in Soong and Kati conventions specifically for Android 15 build, prebuilts, toolchain, and bionic directories to prevent hallucinated paths.

When should I check visibility flags for Android.bp module linking failures?▼

Check visibility flags when encountering module linking failures or depends on disabled module errors. Adjusting visibility in Android.bp files allows permitted modules to access dependencies across different build directories.