skills.rest
himattm
himattmCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

android-probe-logging

Insert ephemeral Log.d probes and capture sentinel logs in logcat to verify Android code path execution.

7|Updated Apr 15, 2026
Search Tags:#debugging#logging#instrumentation#android#probe#logcat
One-click install
npx skills add https://github.com/himattm/skills --skill android-probe-logging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-probe-logging
Source: https://github.com/himattm/skills/tree/main/plugins/android/skills/android-probe-logging
Command: npx skills add https://github.com/himattm/skills --skill android-probe-logging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prove that a specific Android code path actually ran by inserting ephemeral Log.d probes with a unique sentinel, redeploying the app, and filtering logcat to confirm execution.

Core Features & Use Cases

  • Ephemeral probes with a unique sentinel tag that can be cleaned up after testing.
  • Logcat-based verification of execution order and data flow across branches, callbacks, and coroutines.
  • Safe cleanup: detect and remove all probes before concluding the investigation.

Quick Start

Insert a unique probe tag into a suspect code path, redeploy the app, trigger the scenario to generate logs, and remove every probe before finishing.

Frequently Asked Questions about android-probe-logging

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

FAQPage Schema
How do I verify an Android code path actually executed at runtime?▼

Verify an Android code path by inserting ephemeral Log.d probes with a unique sentinel, redeploying the app, and filtering logcat to confirm execution. This proves the specific code path ran by capturing the sentinel log output.

What is the best way to trace execution order across Android coroutines and callbacks?▼

Tracing execution order across Android coroutines and callbacks is done by adding ephemeral probe logs with a unique sentinel tag and filtering logcat. This verifies execution order and data flow across branches during runtime scenario testing.

How do I safely clean up debug logging probes after investigating an Android issue?▼

Safely clean up debug logging probes by detecting and removing every inserted Log.d probe before concluding the investigation. The ephemeral probes use a unique sentinel tag to ensure complete cleanup before finishing the runtime verification.

Can I use logcat to prove a specific callback fired without permanently changing my codebase?▼

Yes, you can use logcat to prove a callback fired by inserting ephemeral Log.d probes with a unique sentinel tag. After redeploying, triggering the scenario, and confirming execution in logcat, you remove all probes before finishing.

What are the limitations of using ephemeral probe logging for Android debugging?▼

The limitation of ephemeral probe logging is that it requires manually adding sentinel logs, redeploying the app, and removing every probe before finishing. This manual instrumentation process must be repeated for each specific code path investigation.

Related Skills

Explore More Software Engineering Skills→
asnar00asnar00
1

eos-watch-logs

Stream real-time Android app logs from a connected device to console and device-logs.txt.

Community
Intermediate
aubrian-haliliaubrian-halili

explore

Trace execution paths, dependencies, and data flow in codebases.

Community
Intermediate
sudatsudat

DebugRuntime

Identify runtime bugs by collecting execution data and applying minimal code changes.

Community
Advanced
AcendasAcendas
3

ad-attach

Attach the Android debugger to a running process by pid or package.

Official
Advanced