android-qa-verification
This skill is used to verify Android features against acceptance criteria, catch regressions and define tests that reflect real device behaviour.
Best use case
android-qa-verification is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
This skill is used to verify Android features against acceptance criteria, catch regressions and define tests that reflect real device behaviour.
Teams using android-qa-verification should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/android-qa-verification/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How android-qa-verification Compares
| Feature / Agent | android-qa-verification | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill is used to verify Android features against acceptance criteria, catch regressions and define tests that reflect real device behaviour.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Android QA and Verification Skill ## Purpose Ensure implemented Android features behave correctly, survive lifecycle changes and match acceptance criteria on real devices and emulators. ## When to Use Use this skill after implementation work or when bugs or regressions are suspected. ## Outputs - Behaviour-based test plan - Unit, instrumentation and UI test ideas - Edge-case scenarios - Reproduction steps - Focused fix suggestions ## Procedure 1. Take the acceptance criteria from product shaping and turn each into one or more test cases. 2. Identify Android-specific edge conditions: - Configuration changes (rotation, theme change). - Process death and recreation. - Timezone changes and daylight saving shifts if times are involved. - App backgrounding and resuming. 3. Plan tests at appropriate levels: - Unit tests for repositories and ViewModels. - Instrumentation or UI tests for flows through Composables and navigation. - Manual test steps where automation is difficult (for example notifications). 4. Validate migrations: - Describe steps to upgrade from an old database version to the new one. - Confirm existing data is preserved and new fields behave as expected. 5. For each bug: - Provide a minimal, deterministic reproduction path. - Map the likely layer (UI, ViewModel, repository, database, platform integration). - Suggest a targeted change, not a refactor. ## Guardrails - Do not propose architectural rewrites. - Do not rely on brittle UI tests that mirror implementation details closely. - Focus on user-visible behaviour, data integrity and stability across lifecycle events.
Related Skills
implementing-android-code
This skill should be used when implementing Android code in Bitwarden. Covers critical patterns, gotchas, and anti-patterns unique to this codebase. Triggered by "How do I implement a ViewModel?", "Create a new screen", "Add navigation", "Write a repository", "BaseViewModel pattern", "State-Action-Event", "type-safe navigation", "@Serializable route", "SavedStateHandle persistence", "process death recovery", "handleAction", "sendAction", "Hilt module", "Repository pattern", "implementing a screen", "adding a data source", "handling navigation", "encrypted storage", "security patterns", "Clock injection", "DataState", or any questions about implementing features, screens, ViewModels, data sources, or navigation in the Bitwarden Android app.
android-agent-skills
Production-ready Agent Skills framework for Android Kotlin development. Provides Clean Architecture patterns, Jetpack Compose best practices, validation DSL, MVI state management, error handling, and AI-powered code generation. Use when building Android apps with quality standards, generating ViewModels, Repositories, UseCases, Compose screens, or writing pure Kotlin Agent Skills.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
android-workflow-beta
Generate GitHub Actions workflow for beta testing track deployment
android-screenshot-automation
Setup automated screenshot capture for Play Store using Fastlane Screengrab
android-playstore-publishing
Complete workflow generation - orchestrates internal, beta, and production deployment workflows
android-emulator-skill
Production-ready scripts for Android app testing, building, and automation. Provides semantic UI navigation, build automation, accessibility testing, and emulator lifecycle management. Optimized for AI agents with minimal token output. Android equivalent of ios-simulator-skill.
adb-android-control
Comprehensive Android device control via ADB (Android Debug Bridge). Use when user asks about: Android device management, app installation/uninstallation, APK operations, package management, file transfer (push/pull), screenshots, screen recording, input simulation (tap/swipe/text/keyevents), shell commands, logcat viewing, device info (battery/memory/storage), automation scripts, wireless ADB connection, scrcpy mirroring. Keywords: adb, android, phone, tablet, device, apk, install app, uninstall app, screenshot, screen record, tap, swipe, type text, keyevent, logcat, push file, pull file, shell, package, activity, intent, broadcast, dumpsys, getprop, settings, input, sendevent, monkey, am start, pm list, device info, battery status, wireless adb, connect device.
acceptance-criteria-verification
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
android-restart-app
Restart the Android app on connected device without rebuilding. Force-stops and relaunches the app remotely. Use when testing changes that don't require rebuild, or refreshing app state.
android-playstore-api-validation
Create and run validation script to test Play Store API connection
agent-ops-article-verification
Systematically deconstruct written content into verifiable claims, validate each using search/documentation, and facilitate informed discussion through structured interviewing.