skills.rest
Acendas
AcendasOFFICIAL
Explore all skills by this author →
GitHub

ad-trace

Trace Android code paths by instrumenting logpoints across a suspect call graph.

3|Updated May 10, 2026
Search Tags:#debugging#timeline#trace#instrumentation#android#call-graph#logpoints
One-click install
npx skills add https://github.com/Acendas/android-debugger --skill ad-trace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ad-trace
Source: https://github.com/Acendas/android-debugger/tree/main/skills/ad-trace
Command: npx skills add https://github.com/Acendas/android-debugger --skill ad-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Android debugging often stalls at inferring code paths; this skill enables tracing through a suspect graph by generating and collecting a timeline of logpoints without stepping the VM.

Core Features & Use Cases

  • Logpoint-based tracing across a suspect call graph to capture call order and values without stopping the VM.
  • Plan-driven instrumentation using a predefined template to systematically place logpoints at entry points and key operators.
  • Use Case: Diagnose an ordering bug or race by comparing the harvested timeline against expected sequences and identifying missing or extra invocations.

Quick Start

Attach an Android debugger to the target app and apply the prepared ad-trace plan to harvest a timeline of calls.

Frequently Asked Questions about ad-trace

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

FAQPage Schema
How do I trace an Android code path without stepping through the VM?▼

You can trace Android code paths by placing logpoints across a suspect call graph using a plan-driven template, which harvests a timeline of calls and values without stopping the VM.

What is logpoint-based tracing for Android debugging?▼

Logpoint-based tracing is a debugging technique that instruments entry points and key operators across a suspect call graph to capture call order and values, producing a timeline for diagnosing ordering bugs and races.

How do I debug an Android race condition using a call graph?▼

Apply a predefined plan template to place logpoints across the suspect call graph, then harvest the timeline to compare actual call sequences against expected ones to identify missing or extra invocations.

Do I need an attached debugger to trace Android call paths?▼

Yes, logpoint-driven tracing requires an attached Android debugger to instrument the target app and collect the timeline of calls from the predefined plan template.

Can I trace value provenance in an Android app using logpoints?▼

Yes, by instrumenting logpoints at key operators across a suspect call graph starting from a seed location, you can harvest a timeline that captures value provenance and call order.

When should I not use logpoint tracing for Android debugging?▼

Logpoint tracing is designed for diagnosing ordering bugs, races, and value provenance in a known app from a seed location, so it is not suited for exploring completely unfamiliar code paths without a suspect graph.

Related Skills

Explore More Software Engineering Skills→
AcendasAcendas
3

ad-status

Read Android debugger session status, target app, PID, and JDWP port.

Official
Basic
richardnpaulrichardnpaul

skill-comply

Generate compliance reports by classifying agent tool calls against behavioral specs.

Community
Advanced
manuelbrandner85manuelbrandner85

trailmark

Parse source code into directed graphs for security-focused static analysis.

Community
Advanced
justinsenseijustinsensei
1

runtime-debugging

Step through Python and Node.js code with breakpoints and inspection.

Community
Intermediate