仓库原始内容
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
OPSX: Trace Log
This skill is a thin wrapper around the opsx trace-log command. Refer to that file for the complete workflow.
Instrument the call chain of a suspected code path with structured trace logs, then guide log capture and analysis to diagnose runtime issues. All instrumentation is removed before the session ends.
Input: The argument after /opsx:trace-log is the entry point, flow description, or suspicion. If nothing is provided, will be prompted.
Quick Reference
- Collect the instrumentation target — entry point, suspicion, scope
- Discover the call chain —
codegraph explore "<entry point>" - Detect the logging framework — Timber / android.util.Log / project utility
- Define trace-logging contract — TAG, log level, entry/exit/key-state/exception logs
- Performance guardrail — detect high-frequency / looping patterns
- Instrument the call chain — add trace logs
- Provide log-capture instructions —
adb logcatfilter command - Analyze captured logs — sequence, timing, thread, state, lifecycle checks
- Cleanup (mandatory) — remove all instrumentation markers
See commands/opsx/trace-log.md for full details.
