免费在 GitHub 公开

r8-analyzer

Analyzes Android build files and R8 keep rules to identify redundancies, broad package-wide rules, and rules that subsume library consumer keep rules. Use when developers want to optimize their app's size, remove redundant or overly broad keep rules, or troubleshoot Proguard configurations.

中文简介正在准备中。当前显示原文说明。

kabirnayeem99/Ktor2Curl

查看安装方法

包含的文件（9）

SKILL.md3.5 KB
references/android/topic/performance/app-optimization/enable-app-optimization.md13.4 KB
references/android/training/testing/other-components/ui-automator.md13.6 KB
references/CONFIGURATION-ANALYZER.md16.9 KB
references/CONFIGURATION.md1.5 KB
references/KEEP-RULES-IMPACT-HIERARCHY.md3.1 KB
references/REDUNDANT-RULES.md8.5 KB
references/REFLECTION-GUIDE.md4.3 KB
references/REPORT_FORMAT.md2.0 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Step 1. Setup and configuration check

Inspect build.gradle, build.gradle.kts, and gradle.properties.
Use references/CONFIGURATION.md to identify missing optimizations.
AGP : If < 9.0, suggest migration to 9.0 for build time improvement performance
Full Mode : Verify android.enableR8.fullMode=false is removed from gradle.properties.

Step 2. Analysis path selection

Inspect build.gradle, build.gradle.kts, and gradle.properties and libs.versions.toml to get the R8 version
If R8 >= 9.3.7-dev : Proceed to Path A (Quantitative).
If R8 < 9.3.7-dev : Proceed to Path B (Heuristic).

Path A: Quantitative data generation (R8 >= 9.3.7-dev)

Check requirements : Python and protobuf package are mandatory.
Generate and analyze : You MUST run the shell commands described in references/CONFIGURATION-ANALYZER.md to generate the proto file using R8 configuration analyzer, convert it to json and analyze the result.
Report : Rely entirely on the generated file analysis.txt for scores and rule impact metrics. Proceed to Step 3.

Path B: Heuristic evaluation and recommendation (R8 < 9.3.7-dev)

(Use ONLY if quantitative data generation is not possible)

Manual evaluation : Inspect proguard-rules.pro.
Library check : Compare rules against references/REDUNDANT-RULES.md. Suggest Remove for bundled rules.
Custom rule check : Use references/KEEP-RULES-IMPACT-HIERARCHY.md and references/REFLECTION-GUIDE.md to prioritize and evaluate. Suggest Refine for broad rules (for example, package-wide).
Validation : Suggest Macrobenchmark tests using UI Automator for any proposed changes. Proceed to Step 3.

Step 3. Report generation

Format : Follow references/REPORT_FORMAT.md strictly.
Input: Extract metrics (Scores, Impacts, Example Classes) directly from generated file analysis.txt if using Path A, or from manual findings if using Path B.
Output : Output ONLY the raw Markdown report in the chat. Do NOT output conversational filler (for example, "Here is your report..."). Do NOT provide recommendations, next steps, or any other text outside of the sections defined in references/REPORT_FORMAT.md Do NOT mention the path used for analysis of the configuration

Constraints

Strict output limit: The final output MUST strictly be the Markdown report and nothing else.
No code changes: Research and suggest only; Do not modify files.
No redundancy: Do not explain R8 benefits or reference skill internal files in the report.
Focus: Omit sections (for example, Subsumed Rules, Configuration) if no issues or items are found.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

adaptive

免费

Instructions to make or update an app's UI so that it adapts to different Android devices including phones, tablets, foldables, laptops, desktop, TV, Auto and XR. It includes how to handle different window sizes, pointing devices (such as mouse) and text entry devices (such as keyboard) using the Compose MediaQuery API. It also covers multi-pane layouts using Navigation3 Scenes, adaptive UI components (such as buttons) with varying target sizes, and adaptive layouts (including navigation areas - nav rails and nav bars) using the Compose Grid and FlexBox APIs.

中文简介正在准备中。当前显示原文说明。