r8-analyzer

Analyze Android R8 and ProGuard keep rules for optimization-blocking redundancies.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/inehemiasm/AiAssistant --skill r8-analyzer-inehemiasm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: r8-analyzer
Source: https://github.com/inehemiasm/AiAssistant/tree/main/skills/r8-analyzer
Command: npx skills add https://github.com/inehemiasm/AiAssistant --skill r8-analyzer-inehemiasm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps Android developers reduce app size and improve optimization by finding redundant, overly broad, or harmful R8 and ProGuard keep rules.

Core Features & Use Cases

  • R8 Configuration Analysis: Reviews Gradle configuration, R8 versions, and optimization settings to identify missing or incorrect setup.
  • Keep Rule Evaluation: Detects broad package rules, redundant library rules, and subsumed rules that limit shrinking, optimization, or obfuscation.
  • Use Case: Analyze an Android release build configuration to identify which keep rules can be removed or refined for better app performance.

Quick Start

Analyze my Android project R8 configuration and generate a report of redundant keep rules and optimization issues.

Frequently Asked Questions about r8-analyzer

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

FAQPage Schema
How do I find redundant ProGuard keep rules in my Android project?

To find redundant ProGuard keep rules, analyze your Android R8 configuration to detect broad package rules and subsumed preservation settings that limit code shrinking. This process generates an actionable report identifying which keep rules can be removed for app size reduction.

Why does my Android release build have a large app size despite R8 minification?

Android release build size remains large despite R8 minification when overly broad keep rules prevent code shrinking and obfuscation. Analyzing your R8 configuration identifies optimization-blocking rules and redundant library settings that restrict the minification process.

How do I analyze R8 configuration settings in a Gradle project?

To analyze R8 configuration settings in a Gradle project, inspect the build files to review R8 versions and optimization setup. This reference-based evaluation detects missing configurations and identifies harmful keep rules restricting app optimization.

Can I use R8 analysis to troubleshoot obfuscation issues in Android apps?

Yes, you can use R8 analysis to troubleshoot obfuscation issues by evaluating your keep rules for redundant or overly broad preservation settings. This identifies configurations that incorrectly limit R8 obfuscation and shrinking during release build tuning.

What is the best way to optimize R8 keep rules for Android app size reduction?

The best way to optimize R8 keep rules for app size reduction is to analyze your Android build configuration to locate subsumed and redundant library rules. Refining these broad package rules improves R8 shrinking and generates an actionable optimization report.

When should I not use broad package keep rules in ProGuard configuration?

You should not use broad package keep rules in ProGuard configuration when they subsume more specific rules and block R8 shrinking. Analyzing these R8 configurations reveals which overly broad preservation settings limit optimization and increase app size.