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.
Best use case
android-restart-app is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using android-restart-app 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-restart-app/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How android-restart-app Compares
| Feature / Agent | android-restart-app | 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?
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.
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 Restart App ## Overview Restarts the Android app on a connected device by force-stopping the existing instance and launching it again. This is useful for testing configuration changes, clearing app state, or refreshing the app without rebuilding. ## When to Use Invoke this skill when the user: - Asks to "restart the Android app" - Wants to "reload the app" - Says "relaunch on device" - Mentions refreshing or resetting the Android app - Wants to test without rebuilding ## Prerequisites - Android device connected via USB - App must be installed on the device (use android-deploy-usb first if not) - USB debugging enabled - ADB installed - Device authorized ## Instructions 1. Navigate to the Android app directory: ```bash cd path/to/android/app ``` 2. Run the restart script: ```bash ./restart-app.sh ``` 3. The script will: - Force-stop the running app with `adb shell am force-stop` - Launch the app again with `adb shell am start` - Activate it (bring to foreground) 4. Inform the user: - The app has been restarted on the device - This does NOT rebuild - only restarts the existing installation - Use android-deploy-usb if code changes need to be deployed first ## Expected Output ``` 🔄 Restarting NoobTest on device... ✅ App restarted ``` ## How It Works The script uses: - `adb shell am force-stop com.miso.noobtest` to kill the app process - `adb shell am start -n com.miso.noobtest/.MainActivity` to launch again ## When to Use vs Deploy **Use restart-app when**: - Testing configuration files or assets that don't require rebuild - Clearing app state (memory, caches) - You just want to refresh the running app - Changes are external (server-side, network config, etc.) **Use android-deploy-usb when**: - You changed Kotlin code - You added/modified UI (Compose) - You updated dependencies in build.gradle.kts - Any code that needs recompilation ## Common Issues **"no devices found"**: - Check USB connection - Ensure USB debugging is enabled - Verify device authorized: `adb devices` - Try: `adb kill-server && adb start-server` **App not installed**: - Run android-deploy-usb first to build and install - Verify app on device home screen or app drawer **App doesn't start**: - Check logcat for errors: `adb logcat | grep NoobTest` - Verify MainActivity class name matches package - Check app permissions if needed ## Speed This is very fast (< 2 seconds) since there's no build step. It's ideal for rapid iteration when testing non-code changes or clearing app state. ## Package Name The script is configured for the specific app's package name. For Firefly/NoobTest, this is `com.miso.noobtest`. Different apps will have different package names configured in build.gradle.kts under `applicationId`. ## Force-Stop Note `adb shell am force-stop` is a clean shutdown that: - Stops all app processes - Clears memory but keeps app data - Safer than killing process with `kill` command - Recommended way to stop Android apps during development
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.
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.
android-qa-verification
This skill is used to verify Android features against acceptance criteria, catch regressions and define tests that reflect real device behaviour.
android-playstore-api-validation
Create and run validation script to test Play Store API connection
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
moai-lang-r
R 4.4+ best practices with testthat 3.2, lintr 3.2, and data analysis patterns.
moai-lang-python
Python 3.13+ development specialist covering FastAPI, Django, async patterns, data science, testing with pytest, and modern Python features. Use when developing Python APIs, web applications, data pipelines, or writing tests.