android-strictmode-probe

Enable StrictMode in Application.onCreate to log main-thread policy violations.

7|Updated Apr 15, 2026

Search Tags:#performance #debugging #android #logcat #main-thread #strictmode

Ready to run

npx skills add https://github.com/himattm/skills --skill android-strictmode-probe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: android-strictmode-probe
Source: https://github.com/himattm/skills/tree/main/plugins/android/skills/android-strictmode-probe
Command: npx skills add https://github.com/himattm/skills --skill android-strictmode-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill exposes silent, performance-robbing violations that don’t crash the app by temporarily enabling StrictMode and guiding you to fix issues on the main thread.

Core Features & Use Cases

Temporarily install StrictMode in Application.onCreate to surface Disk I/O, network, and leaked-objects on the main thread.
Drive suspect flows in the app to capture violations in logs with stack traces pointing to your code.
Provide a clean removal and cleanup process to revert app behavior after fixes.

Quick Start

Install the probe in your app's Application.onCreate, run through a suspect flow, and review StrictMode logs to identify violations.

Frequently Asked Questions about android-strictmode-probe

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

FAQPage Schema

How do I detect main thread disk IO and network violations that don't crash my Android app?▼

To detect main thread violations, temporarily enable StrictMode in Application.onCreate to surface silent disk IO, network, and leak issues with penaltyLog, capturing stack traces in logcat without crashing the app.

How does StrictMode expose performance-robbing issues during Android app startup?▼

StrictMode exposes performance issues by installing a temporary top-level thread policy in Application.onCreate that logs violations with stack traces pointing to your code when suspect flows are driven during startup and core interactions.

Can I use StrictMode to find leaked objects on the main thread without causing app crashes?▼

Yes, you can use StrictMode to find leaked objects by applying a temporary policy with penaltyLog only, which reports violations in logcat without triggering application crashes or altering runtime behavior.

What is the best way to clean up StrictMode after fixing main thread violations?▼

The best way to clean up StrictMode is to use a dedicated cleanup gate to revert the temporary policy and remove the probe from Application.onCreate after driving fixes for the identified thread violations.

When do I need to enable StrictMode for Android performance debugging?▼

You need to enable StrictMode when diagnosing silent main thread performance issues during app startup or core interactions, specifically to reveal disk I/O, network operations, and leaked objects that degrade performance without crashing.

Why does StrictMode log stack traces instead of crashing my app during performance debugging?▼

StrictMode logs stack traces instead of crashing because the temporary top-level policy is configured with penaltyLog only, capturing disk IO and network violation details in logcat to guide fixes while maintaining app stability.