codedroid

Plugin codedroid from marketplace codedroid in codedroid-team/codedroid-mcp. Commands read from the repo's manifest — today.

Skills (11)

• app-e2e-bug

  Turn a reported Android app bug into an e2e test case that reproduces it on the real phone through CodeDroid - fails on the current build, passes once fixed, and stays in e2e/TESTCASES.md as a regression test - with the root cause found in the source. Use when the user reports a bug in an app, asks

• app-e2e-cujs

  Write an Android app's critical user journeys (CUJs) for end-to-end testing with CodeDroid into e2e/CUJs.md - each the user's goal, its priority and run mode, and the outcomes visible on the phone that prove it - grouped by the PRD's features, with a coverage table against the test PRD. Use as step

• app-e2e-explore

  Explore an Android app before testing it end to end with CodeDroid - read its UI source for every label, walk each screen on the real phone read-only, and write e2e/EXPLORE.md with exact selectors, traps and account state. Use as step 1 of app-e2e, or when test cases fail with not_found or ambiguous

• app-e2e-maintain

  Keep an app's e2e test cases and CUJs current after the app changes - update labels and steps from the source and the phone, retire cases for removed features, add cases for new screens, and list the CUJs and requirements nothing tests. Use when test cases fail because the UI changed, when asked to

• app-e2e-prd

  Write the test PRD for testing an Android app end to end with CodeDroid - the release question, journeys in scope, non-goals, constraints of driving a real phone, priorities, the app's features with every screen assigned to one, numbered requirements per feature and release criteria - into e2e/PRD.m

• app-e2e-rerun

  Run some of an app's existing e2e test cases on the real phone through CodeDroid - by case id, by CUJ, by feature, by priority (a smoke run), the ones that failed last time, a flaky check, the ones a code change touches, or the same cases on two builds - and report what passed. Use when asked to run

• app-e2e-run

  Run an app's approved e2e test cases on the real phone through CodeDroid, judge each failure as an app bug, a test bug or the environment, and write a test report with screenshots of every case into e2e/reports/<date>/. Use as step 5 of app-e2e, or when asked to run e2e test cases or CUJs on the pho

• app-e2e-testcases

  Turn an app's approved CUJs into test cases an agent can run on the real phone through CodeDroid - start state, steps by exact label, expected outcomes, cleanup, with negative cases for each feature's gates and harmful controls - into e2e/TESTCASES.md. Use as step 4 of app-e2e, when asked to write o

• app-e2e

  End-to-end test an Android app on the user's real phone through CodeDroid, from exploring the app to a release verdict - explore, write a test PRD, critical user journeys (CUJs) and test cases into the app's repo, run them on the phone and report with screenshots. Use when asked to test an app end t

• codedroid-phone

  Drive the user's real Android phone through CodeDroid's MCP tools (get_screen, tap, type_text, swipe, open_app, wait_for, run_task, adb). Use whenever a task means seeing or doing something on the phone - checking a screen, tapping through an app, typing into a field, reading what an app shows, or h

• test-on-device

  Verify an Android app change on the user's real Android phone - build, install, open, drive the changed screens with CodeDroid, check logcat for crashes, run instrumentation tests, and report what was seen. Use after changing Android app code, when asked to test, reproduce or verify something on a d

MCP servers (1)

• codedroid

  runs: npx -y @codedroid/[email protected]

Similar plugins