DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to analyze R8 shrinking config with the r8-analyzer skill with Skills

Install the r8-analyzer skill so an agent can review R8 configuration in an Android project.

  • Top pick
  • Software and DevOps
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code
  • Codex
  • Gemini CLI

Who it is forAndroid developer whose release build is shrunk or obfuscated with R8 and who needs a second look at the configuration.

The problemR8 rules are hard to check by hand, and LLMs are noted in the README as underperforming on some workflows.

The outcomeThe agent works from the r8-analyzer skill's instructions when it reviews the project's R8 setup.

What you need first

  • Android CLI, documented at developer.android.com/tools/agents/android-cli
  • An AI agent that reads skills, such as Claude Code, Codex, or Gemini
  • An Android project to work on

Steps

  1. Install Android CLI from developer.android.com/tools/agents/android-cli.
  2. Run android skills add r8-analyzer --project=. in the project root.
  3. Open your agent in the project directory.
  4. Ask the agent to review the R8 configuration and explain each suggested change.
  5. Build the release variant and test it before you accept any rule change.

Prompt for your agent

Using the android/skills repository and its r8-analyzer skill, review the R8 configuration in <project path> and list suggested changes with a reason for each. Verify by building the release variant of the app and confirming it still runs.

Caveat. The README says AI can make mistakes, so every suggested R8 change needs to be checked by a build and a test run.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page