run-action

Execute the learned action: $ARGUMENTS

What this command does

/rn-dev-agent:list-learned-actions lists what's available; /rn-dev-agent:run-action actually replays one. Together they implement the artifact-first protocol from feedback_execute_artifacts_before_manual.md: list → match → run, before composing any device_* primitives manually.

The action name is matched against the inventory's flow field (filename without .yaml). Substring + case-insensitive — task-create will match wizard-create-task if it's the only candidate; ambiguity errors otherwise.

Argument parsing

The first positional arg is the action name (required). Subsequent args are parsed into the cdp_run_action request:

• -e KEY=VALUE — environment variable for ${KEY} placeholders in the flow. Keys must match [A-Z_][A-Z0-9_]* (Maestro convention) — anything else is rejected by cdp_run_action / maestro_run (GH #116).
• --platform <ios|android> — must match the current ready session; omitted values are filled from that session
• --no-auto-repair — opt out of cdp_repair_action retry on SELECTOR_NOT_FOUND (default: auto-repair on)

Example calls:

/rn-dev-agent:run-action wizard-create-task -e TITLE="Buy milk" -e PRIORITY=high -e TAG=feature -e DESC="Test"
/rn-dev-agent:run-action mark-all-done --platform android
/rn-dev-agent:run-action mark-all-done --no-auto-repair    # surface the raw failure without patching

Protocol

1. Parse arguments. First word of $ARGUMENTS is the action name. Detect --platform, --no-auto-repair, and collect every -e KEY=VALUE pair into a params object (key must match [A-Z_][A-Z0-9_]*; reject malformed early — cdp_run_action will refuse them anyway, but catching at parse time gives a clearer error). Treat anything else as a passthrough flag.

2. Resolve the action via the script (single source of truth — never glob .rn-agent/actions/ directly):

   ACTION_NAME="<first-arg>"
   RESULT=$(node "${CLAUDE_PLUGIN_ROOT}/rn-dev-agent-core/dist/learned-actions.js" \
     --json --section b \
     --workspace-root "$PWD" --memory-cwd "$PWD" \
     --filter "$ACTION_NAME")
   COUNT=$(echo "$RESULT" | jq '.sections.flows.count')
   

   • 0 matches: stop. Tell the user what they searched for, list the closest 5 alternatives by running the script again with a broader filter (or no filter), and suggest creating the flow via /rn-dev-agent:test-feature.
   • >1 match: stop. Print the candidates with their full paths and ask the user to disambiguate (e.g. by passing the full filename without .yaml).
   • 1 match: continue to step 3.