Identify redundant and overly broad R8 keep rules in Android projects.
npx skills add https://github.com/tajemniktv/TajsOS --skill r8-analyzer-tajemniktv
Please help me install this Agent Skill. Skill: r8-analyzer Source: https://github.com/tajemniktv/TajsOS/tree/main/.agent/skills/r8-analyzer Command: npx skills add https://github.com/tajemniktv/TajsOS --skill r8-analyzer-tajemniktv
Android apps often bloat due to redundant, overly broad, or unnecessary R8/ProGuard keep rules that block code shrinking and optimization, leading to larger download sizes and worse runtime performance.
Use the r8-analyzer skill to review your Android project's ProGuard keep rules and receive a prioritized list of changes to reduce your app's final size.
High-intent search queries and answers about installing and using this skill.
To identify redundant ProGuard keep rules increasing Android app size, audit your build configuration against embedded library consumer rules. This process flags rules for common libraries like AndroidX and Gson that are already covered, allowing you to remove unnecessary bloat without breaking functionality.
R8 code shrinking may not reduce Android app size effectively when overly broad package-wide keep rules or inversion operator misuse prevent optimization. Auditing your configuration for subsuming rules helps R8 shrink large swathes of previously blocked code.
To narrow keep rules for reflection-dependent code without breaking functionality, analyze your code reflection patterns against your current ProGuard configuration. This generates specific, narrow keep rules that preserve runtime behavior while maximizing R8 optimization potential.
You can remove keep rules for common libraries like Retrofit and Room if they duplicate embedded library consumer rules. Auditing your ProGuard configuration detects these redundant rules, allowing safe removal to reduce final app size without causing runtime errors.
The best way to audit an Android project's R8 configuration for release builds is to review keep rule files against embedded library consumer rules and code reflection patterns. This generates a prioritized list of rule modifications to reduce final app size.
Yes, r8-analyzer works with Android application projects using R8 or ProGuard for release builds. It audits your build configuration and keep rule files to generate a prioritized list of modifications that shrink app size without breaking reflection-dependent features.
drewid74Analyze Android R8 keep rules for redundant and subsuming rules.
yash-gargAnalyze Android R8 configurations and keep rules to identify optimization blockers.
inehemiasmAnalyze Android R8 and ProGuard keep rules for optimization-blocking redundancies.
new-silvermoonAnalyze Gradle build scans to identify and reduce Android build bottlenecks.
