Trace Investigation
Independent PiSkill directory guide. The original prompt remains hosted by Microsoft PromptKit.
What does this prompt do?
Uses logs, traces, timing, identifiers, and code paths to reconstruct a failing request or workflow and isolate the most likely root cause.
Primary use case
Investigate an application failure from trace and log evidence.
Expected output
A reconstructed failure path with evidence, uncertainty, and next checks.
Inputs or variables
- trace
- logs
- system context
Related prompts
Compiler Warning Fixer
Investigates compiler warnings, separates root causes from symptoms, applies behavior-preserving fixes, and verifies that warning suppression is justified when used.
Exhaustive Bug Hunt
Runs a systematic bug investigation across changed behavior, edge cases, error paths, concurrency, state, and integration boundaries with evidence requirements.
Spec Kit Bug Assessment
Assesses a reported defect against repository evidence, expected behavior, reproduction details, impact, and implementation context before a fix is attempted.
Bug Investigation
Guides a focused investigation from symptoms through repository evidence to a defensible root-cause hypothesis.
CI Failure Root Cause
Traces a continuous-integration failure through logs, configuration and recent changes before proposing a targeted repair.
Azure DevOps Build Investigation
Collects Azure DevOps build information and organizes status, stages, failures, logs, and relevant repository context for efficient diagnosis.