skills.rest
Lightrion
LightrionOFFICIAL
Explore all skills by this author →
GitHub

aosp-platform-development

Answer AOSP framework questions with version-anchored citations from Lightrion MCP.

19|4|Updated May 16, 2026
Search Tags:#semantic search#android#aosp#safety analysis#code citations#version diff#framework code
One-click install
npx skills add https://github.com/Lightrion/skills --skill aosp-platform-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aosp-platform-development
Source: https://github.com/Lightrion/skills/tree/main/aosp-platform-development
Command: npx skills add https://github.com/Lightrion/skills --skill aosp-platform-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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?"

Frequently Asked Questions about aosp-platform-development

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

FAQPage Schema
How do I find specific AOSP framework code changes between Android versions?▼

To find AOSP framework code changes between versions, use semantic search to locate relevant logic in targeted release tags, then perform a version diff to pinpoint exact divergences across Android 13–16. This grounds every finding in concrete file paths and specific release anchors.

Why does Doze behavior or JobScheduler exemptions differ across Android releases?▼

Doze behavior or JobScheduler exemptions differ across Android releases due to regressions or high-risk changes like fault defaults and permission gates. You can locate the exact logic in a targeted AOSP release and compare it with another to pinpoint what changed.

What is the best way to debug deep Android platform behavior in frameworks/base or packages/services?▼

The best way to debug deep Android platform behavior in frameworks/base or packages/services is using semantic retrieval to quickly find relevant AOSP code, confirming by reading full chunks, and tracing symbols via cs.android.com navigation links for auditable evidence.

Can I investigate AAOS subsystems using AOSP semantic search?▼

Yes, you can investigate AAOS subsystems using AOSP semantic search. The skill applies to reading, debugging, and modifying platform code across vendor/, hardware/interfaces/, and system/, providing version-cited truth and explicit release anchoring for automotive platform investigations.

How do I trace AOSP symbols beyond what semantic retrieval provides?▼

To trace AOSP symbols beyond semantic retrieval, use the cs.android.com jump-to-definition links included in MCP results. This helps you navigate and trace symbols across frameworks/, packages/services/, and other AOSP directories for deeper verification.

What safety divergences should I look for when comparing AOSP releases?▼

When comparing AOSP releases, look for safety divergences like regressions and high-risk changes including fault defaults, permission gates, callback lifecycle issues, and isolation boundary mistakes. Explicitly flag these changes with confirmation across versions to ensure platform stability.

Related Skills

Explore More Software Engineering Skills→
steipetesteipete
385.7k

qmd

Index local files and search them with BM25, vector, and hybrid queries.

Community
Advanced
YeaChan05YeaChan05

review

Analyze code diffs to determine a post-verify QA gate outcome.

Community
Intermediate
philo-grovesphilo-groves
12

maxtac-android-runtime-debugging

Capture Android runtime evidence via ADB, logcat, JDWP, and Frida.

Community
Advanced
lbrutonlbruton
8

search-code

Search codebases using tiered semantic and literal search strategies.

Community
Intermediate