adb
Use ADB commands to interact with an Android device or emulator to complete a user-defined mission. Operates in a screenshot-act-verify loop until the mission is accomplished.
Usage:
/adb <mission>— Describe what you want done on the device (e.g., "open Settings and enable Dark Mode")
Prerequisites:
adbmust be in PATH- A device or emulator must be connected
Instructions:
-
Verify ADB connectivity:
- Run
adb devicesand confirm at least one device is listed (not "unauthorized") - If no device is found, inform the user and STOP
- If multiple devices are found, use
AskUserQuestionto ask which device to target, then pass-s <serial>to all subsequentadbcommands
- Run
-
Understand the mission:
- Parse
$ARGUMENTSas the mission description - If
$ARGUMENTSis empty, useAskUserQuestionto ask what the user wants to accomplish on the device
- Parse
More from morphet81/cheat-sheets
translate-pdf
Translate a PDF document from one language to another. Extracts text to structured Markdown, translates it, and builds a new translated PDF. Requires a Python environment with pymupdf, markdown, and weasyprint.
80create-jira-ticket
Create a JIRA ticket from user instructions via acli. Uses project from the current branch when possible, lists project epics, recommends the best epic, asks confirmation before creating, uses ADF descriptions, and can attach Figma designs via the Jira integration.
80localise
Generate an HTML translation helper page for Lokalise. Use when the user provides English text (singular/plural) and wants translations across all 23 supported languages, rendered as an interactive HTML page with copy buttons. Triggers on phrases like "translate for Lokalise", "generate translations", "translation table", or when the user provides English strings and mentions languages/i18n/localization.
79update-jira-ticket
Compare the JIRA ticket description to changes made in the current branch and propose description edits and/or comments to keep the ticket accurate and well-documented.
79verify-test-cases
Verify test cases in all test files modified since branching out from base branch. Checks that test cases make sense, have no duplications, and provide meaningful coverage. Spawns parallel agents for multi-file analysis. After the user confirms test-case changes, runs coverage (npm test:coverage or Jest/Vitest fallback) and fixes tests until coverage passes.
79merge-base-branch
Select base branch (from .agent, git history, or main), fetch, stop if already up to date, commit all WIP, merge, resolve conflicts, then lint, tests at 100% coverage, and build—with commits after each fix phase.
79