android-source-search

You can fetch AOSP source code directly to inspect framework internals and hidden APIs when official documentation falls short. This Skill retrieves specific files like View.java from AOSP repositories to illuminate implementation details and clarify ambiguous API behavior.

Fetching AndroidX source trees allows direct inspection of library internals and default attributes. By retrieving specific paths from raw.githubusercontent.com, you can review the actual implementation logic to understand undocumented behaviors and derive correct usage patterns.

Yes, you can locate unknown paths in the Android source tree using directory listings. When the exact path is ambiguous, the Skill applies directory listing queries via gh api to discover the correct file locations before fetching the source code.

Accessing @hide APIs requires fetching the AOSP framework source to inspect their internal mechanics. The Skill retrieves relevant source files directly from Gitiles, allowing you to review hidden API declarations and implementation details missing from public documentation.

No, fetching Android framework internals does not require knowing the exact repository structure beforehand. The Skill handles path discovery using directory listings and Gitiles fetch methods to locate targets within AOSP or AndroidX when paths are unknown.

The main limitation is presenting relevant highlights within the allowed frontmatter context. Large AOSP source files must be summarized rather than displayed in full, meaning the Skill extracts and presents only the key implementation details and framework internals.