android-ui-regression-checker

Diagnose Android UI defects and regression risks across Views and Jetpack Compose.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill android-ui-regression-checker-te-quanbzhang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-ui-regression-checker
Source: https://github.com/TE-QuanBZhang/skills-pool/tree/main/ai-coding/skills/android-ui-regression-checker
Command: npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill android-ui-regression-checker-te-quanbzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Android UI bugs like layout breakage, click failures, RecyclerView flicker, and Compose recomposition issues are hard to classify and risky to fix without a structured investigation process. This Skill guides a systematic diagnosis that identifies the failure mode, locates the suspect UI layers, and assesses regression risk across devices, themes, and locales. ## Core Features & Use Cases - UI Bug Classification: Categorizes defects as layout, state, rendering, adapter, interaction, theme, or localization issues before any fix is attempted. - Rendering Path Inspection: Traces state-to-UI mapping, adapter binding, Compose recomposition boundaries, and click handler registration, optionally using CodeGraph for code exploration. - Regression Risk Assessment: Evaluates fixes against screen sizes, dark mode, large fonts, RTL, foldables, and OS version differences, then recommends screenshot or UI tests. - Use Case: After a refactor causes a RecyclerView item to flicker and a button to stop responding in dark mode, use this Skill to classify the failure modes, inspect the adapter binding and theme overlays, and produce a fix plan with a validation matrix. ## Quick Start Use the android-ui-regression-checker skill to investigate why the profile screen layout overlaps in dark mode and recommend a fix with regression validation steps.

Frequently Asked Questions about android-ui-regression-checker

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

FAQPage Schema
How do I debug Android UI layout issues systematically?▼

Start by classifying the bug as a layout constraint, state rendering, interaction, or theme issue, then inspect the rendering path including constraints, visibility logic, and insets. This Skill provides a five-step workflow covering classification, inspection, device factors, fix recommendation, and validation.

How to fix RecyclerView flicker and item rebinding issues?▼

RecyclerView flicker usually comes from unstable item identity or unnecessary full-list refreshes. Use stable IDs, correct DiffUtil callbacks, and targeted updates instead of notifyDataSetChanged, and verify with repeated scroll and rebind checks.

Does this work with Jetpack Compose recomposition problems?▼

Yes, it covers Compose state and recomposition issues including unstable state sources, recomposition-trigger loops, and state hoisting problems. It recommends checking @Stable annotations, remember, derivedStateOf, and ensuring a single source of truth for UI state.

Can CodeGraph analyze Android XML layouts and themes?▼

CodeGraph does not reliably index res/layout, res/values, res/drawable, or AndroidManifest.xml files. For bugs rooted in layout XML, theme inheritance, or resource qualifiers, supplement CodeGraph with rg or find searches on the res directory.

What should I check for dark mode and screen size regressions?▼

Validate fixes across dark mode, large fonts, RTL locales, small screens, landscape, foldables, and OS version differences. Avoid hard-coded dimensions and magic pixel offsets, and add screenshot or UI tests for fragile layouts.