https://developer.android.com/agents/skills/performance/r8-analyzer/skill

You can audit your R8 configuration to quantify keep-rule impact on shrinking, obfuscation, and optimization. By scanning Gradle files and analyzing build output artifacts, this approach pinpoints unnecessary ProGuard or R8 keep rules that reduce optimization effectiveness in release builds.

A quantitative R8 configuration analyzer is a tool that generates evidence-based reports of keep-rule impact on code shrinking. It is needed when you want to remove or refine broad keep rules in your proguard-rules.pro file to reclaim optimization opportunities while ensuring runtime-loaded code still works.

When quantitative analysis is not possible due to unsupported R8 versions, a heuristic fallback evaluates keep rules manually for redundancy and breadth. It checks Gradle settings for common performance blockers like AGP version and full mode flags to guide configuration improvements.

You audit release configuration by scanning Gradle files and flags to validate settings, then generating analysis output artifacts. This produces a strictly formatted raw Markdown report detailing optimization, obfuscation, and shrinking impacts caused by your current keep rules.

Heuristic rule-review relies on manual evaluation of redundancy and breadth using reference guidance rather than generating evidence-based quantitative analysis. This fallback is used only when the R8 version does not support the quantitative configuration analyzer path.