dev-jump

Launch the Android debug app to a target screen via nutrisport:// deep-link.

11|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/satanyakiv/NutriSport --skill dev-jump
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-jump
Source: https://github.com/satanyakiv/NutriSport/tree/main/.claude/skills/dev-jump
Command: npx skills add https://github.com/satanyakiv/NutriSport --skill dev-jump

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Launches the Android debug app directly to a target screen using the nutrisport:// deep-link scheme, enabling fast visual verification without walking through multi-step flows.

Core Features & Use Cases

  • Direct deep-link navigation to a specific screen for rapid design fidelity checks.
  • Supports terminal/static screens (e.g., PaymentCompleted, Details) and quick one-screen verifications across the app.
  • Provides canonical adb commands and gating guidance to ensure correct screen rendering in automated QA sessions.

Quick Start

Use a direct Android deep-link to the target screen with the provided adb command to launch the app on that screen.

Frequently Asked Questions about dev-jump

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I launch an Android debug app directly to a specific screen for visual QA?▼

To perform visual QA, launch the Android debug app to a target screen using the nutrisport:// deep-link scheme via an adb command. This navigates directly to the specified screen for rapid design fidelity checks.

What do I need to use a deep-link to test terminal Android screens like PaymentCompleted?▼

Testing terminal Android screens via deep-link requires the debug package com.portfolio.nutrisport.debug installed, the deep-link track present, and adherence to prerequisites outlined in the SKILL.md to correctly reach the target screen.

When should I use deep-link navigation instead of manual clicks for Android app verification?▼

Use deep-link navigation for Android app verification when you need to bypass multi-step flows. It is ideal for one-screen visual checks across various sections and verifying static designs behind complex navigation paths.

Does this visual verification method work for any Android screen or only specific ones?▼

This visual verification method works for terminal and static screens like PaymentCompleted or Details, as well as quick one-screen visual checks across various app sections, provided the deep-link track exists.

Why is my Android deep-link not reaching the target screen during automated QA?▼

An Android deep-link may fail to reach the target screen if the deep-link track is missing, the wrong package is used, or the prerequisites in SKILL.md are not followed, which provide gating guidance for correct rendering.