android-reproduce-as-test

Write a failing Android Kotlin/Java test that reproduces a bug before production changes.

7|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/himattm/skills --skill android-reproduce-as-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-reproduce-as-test
Source: https://github.com/himattm/skills/tree/main/plugins/android/skills/android-reproduce-as-test
Command: npx skills add https://github.com/himattm/skills --skill android-reproduce-as-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures that bugs are reproduced with a failing test before any non-trivial production code changes, preventing guesswork and establishing a regression guard.

Core Features & Use Cases

  • Create a failing test that captures the bug's repro path before implementing a fix.
  • Use a red→green workflow to validate changes and maintain a regression guard across refactors.
  • Applicable to Java/Kotlin Android projects and frameworks where stack traces or user reports guide debugging.

Quick Start

Run a failing test to reproduce the bug, then fix the code until the test passes.

Frequently Asked Questions about android-reproduce-as-test

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

FAQPage Schema
How do I write a failing test to reproduce an Android bug before fixing it?

You can reproduce an Android bug by writing a failing test that mirrors the repro path from a stack trace or user report, verifying it fails before any production code changes are applied.

What is the red to green testing workflow for Android Kotlin projects?

The red to green workflow involves creating a failing test to reproduce a bug, then modifying the production code until the test passes, validating the fix and establishing a regression guard.

Can I use stack traces to drive unit tests for Android Java and Kotlin bugs?

Yes, you can use stack traces, user reports, or repro steps to drive the creation of failing unit tests in Android Java and Kotlin projects to pinpoint and verify bug causes.

How do I maintain a regression guard when refactoring Android code?

You maintain a regression guard by keeping the initially failing test that reproduced the bug, ensuring it stays green across future code edits and refactoring efforts.

Why should I create a failing test before patching production code?

Creating a failing test before patching prevents guesswork by confirming the exact cause of the bug, ensuring your subsequent production code changes directly address the validated issue.