Analyze Android R8 keep rules for redundant and subsuming rules.
npx skills add https://github.com/drewid74/ai_skills --skill r8-analyzer-drewid74
Please help me install this Agent Skill. Skill: r8-analyzer Source: https://github.com/drewid74/ai_skills/tree/main/android-r8-analyzer Command: npx skills add https://github.com/drewid74/ai_skills --skill r8-analyzer-drewid74
Redundant or overly broad R8/ProGuard keep rules bloat your APK/AAB and make shrinking harder to reason about, causing slow builds and unnecessary size overhead.
Use the r8-analyzer skill to analyze your Android build and ProGuard/R8 keep rules and generate R8_Configuration_Analysis.md with precise removal/refinement recommendations.
High-intent search queries and answers about installing and using this skill.
Redundant R8 keep rules can be found by scanning your Gradle Android project configuration for library-wide rules that overlap with narrower consumer ProGuard rules. The analysis outputs an ordered list of rules to remove or refine for smaller app packages.
An R8 keep rule impact hierarchy maps how broader keep rules subsume narrower consumer rules. By analyzing this hierarchy, you can pinpoint and remove redundant ProGuard rules that bloat your app while preserving the necessary shrinking behavior.
To narrow broad R8 keep rules targeting common Android libraries, apply reflection-aware guidance that connects remaining rules to actual reflection use. This generates more specific keep rules tailored to your codebase, optimizing the Gradle build configuration.
Yes, you can analyze Gradle-based Android projects by scanning build.gradle, build.gradle.kts, gradle.properties, and proguard configuration files. This identifies redundant keep rules and generates actionable removal or refinement recommendations for your build.
The best way to generate a cleanup plan is to analyze R8 keep rules using an impact hierarchy and reflection guidance. This produces an ordered set of precise per-rule remove or refine instructions, maximizing APK and AAB size optimization.
Unnecessary size overhead often persists because of overly broad or redundant R8 keep rules that prevent the shrinker from removing unused code. Analyzing your ProGuard configuration for subsumption and library-wide rules can pinpoint and resolve this bloat.
premex-abAnalyze Android build files and R8 keep rules to identify redundant or overly broad rules.
hitoshura25Validate Android release builds for signing, obfuscation, and packaging.
tajemniktvIdentify redundant and overly broad R8 keep rules in Android projects.
iadr-devAnalyze Android R8/Proguard keep rules to identify redundant or overly broad rules.
