aosp-platform-development

What problem does it solve?

It helps developers answer deep, correctness-critical questions about Android platform behavior by grounding every claim in the right AOSP release tag instead of relying on vague recollection or brittle keyword searches.

Core Features & Use Cases

• Version-anchored code answers: Produces findings that cite concrete file paths and release tags so differences across Android 13–16 are never blurred.
• MCP-first semantic retrieval: Uses Lightrion MCP semantic search to find relevant AOSP framework code quickly, then confirms by reading full chunks or exact files.
• Safety divergence flagging: Explicitly calls out regressions and high-risk changes between releases (fault defaults, permission gates, callback lifecycle issues, and isolation boundary mistakes), with confirmation across versions.
• cs.android.com linking for navigation: Surfaces the cs.android.com jump-to-definition link included in MCP results to help users trace symbols beyond what semantic retrieval provides.
• Use Case: When debugging why Doze behavior or JobScheduler exemptions differ between Android releases, use this skill to locate the exact logic, confirm it in the targeted release, and compare with another release to pinpoint what changed.

Quick Start

Ask the assistant: "Using AOSP android-16.0.0_r4, where is the code that explains [your issue] in frameworks/base or packages/services, and what changed in android-15.0.0_r36?"