r8-analyzer

Analyze Android R8 keep rules for redundancies and overly broad patterns.

127|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/hanamizuki/solopreneur --skill r8-analyzer-hanamizuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: r8-analyzer
Source: https://github.com/hanamizuki/solopreneur/tree/main/plugins/android-dev/skills/r8-analyzer
Command: npx skills add https://github.com/hanamizuki/solopreneur --skill r8-analyzer-hanamizuki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Android apps often carry redundant or overly broad ProGuard/R8 keep rules that hinder size optimizations. This skill analyzes rule sets to identify inefficiencies and inform remediation.

Core Features & Use Cases

  • Identify redundancies across R8 keep rules and library consumer rules.
  • Detect overly broad patterns and subsuming rules that block optimization.
  • Provide actionable guidance to narrow rules and troubleshoot ProGuard configurations.

Quick Start

Run a scan of your project's Gradle and ProGuard files to generate a keep-rule optimization report.

Frequently Asked Questions about r8-analyzer

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

FAQPage Schema
How do I identify redundant R8 keep rules to shrink my Android APK?

To shrink your Android APK, scan your Gradle build scripts and ProGuard rule files to identify redundant R8 keep rules and replace them with narrow, evidence-based rules.

Why does ProGuard configuration block app size optimization in my Android project?

ProGuard configuration blocks app size optimization when overly broad patterns and subsuming rules prevent R8 from safely pruning unused code across modules and libraries.

How do I analyze library consumer rules that conflict with R8 keep rules?

You can analyze library consumer rules by inspecting Gradle build scripts and evaluating rule sets against the established R8 rules hierarchy to detect overlapping or subsuming rules.

What is the best way to narrow overly broad keep rules in an Android project?

The best way to narrow overly broad keep rules is to generate an optimization report that suggests narrow, evidence-based replacements based on the established rules hierarchy.

Can I use this R8 analyzer to troubleshoot ProGuard configurations across multiple modules?

Yes, you can use this R8 analyzer to troubleshoot ProGuard configurations by evaluating library rules and cleaning up keep rules across modules and libraries.