android-qa

Run detekt, unit tests, and jacoco coverage for Android Gradle projects.

1|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/ChooJeongHo/MovieFinder --skill android-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-qa
Source: https://github.com/ChooJeongHo/MovieFinder/tree/main/.claude/skills/android-qa
Command: npx skills add https://github.com/ChooJeongHo/MovieFinder --skill android-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MovieFinder QA pipeline reduces manual QA overhead by orchestrating static analysis, unit tests, and coverage reporting for Android projects.

Core Features & Use Cases

  • QA Pipeline Orchestration: Runs detekt, unit tests, and jacoco coverage to surface code quality issues early.
  • Progress & Results: Produces summarized results with actionable fixes for failing checks, suitable for CI and local development.
  • Use Case: A developer can push a change and instantly see if it passes all QA gates before merging.

Quick Start

Run the QA pipeline for the MovieFinder Android project to execute detekt, unit tests, and jacoco coverage checks.

Frequently Asked Questions about android-qa

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

FAQPage Schema
How do I automate Android QA with detekt and jacoco coverage in Gradle?

Automate Android QA by orchestrating detekt static analysis, unit tests, and jacoco coverage reports within a Gradle-built project. This pipeline surfaces code quality issues early and produces actionable fixes for failing checks before merging.

Can I run detekt and jacoco locally to catch code quality issues before CI?

Yes, running detekt and jacoco locally enables deterministic QA checks across both CI and local development. You instantly see if your changes pass all QA gates, producing summarized results with actionable fixes for failing checks.

Do I need a specific project structure to run Android unit tests and coverage checks?

Yes, you require a Gradle-based Android project structure with configured detekt, test tasks, and jacoco reports to satisfy the QA pipeline constraints. These prerequisites ensure deterministic QA runs across your local and CI environments.

What is the best way to orchestrate static analysis and unit tests for an Android project?

The best approach is orchestrating a QA pipeline that sequentially runs detekt for static analysis, unit tests for logic validation, and jacoco for coverage reporting. This surfaces code quality issues early with actionable summaries for CI integration.

Why does my Android QA pipeline fail when jacoco coverage reports are missing?

Your Android QA pipeline fails because it requires configured detekt, test tasks, and jacoco reports to satisfy its QA pipeline constraints. Without these Gradle configurations, the deterministic QA run cannot execute or validate coverage gates.