Azure DevOps Build Investigation
Independent PiSkill directory guide. The original prompt remains hosted by Microsoft HVE Core.
What does this prompt do?
Collects Azure DevOps build information and organizes status, stages, failures, logs, and relevant repository context for efficient diagnosis.
Primary use case
Investigate a failed or unexpected Azure DevOps build.
Expected output
A structured build summary with failure evidence and next diagnostic steps.
Inputs or variables
- build identifier
- project
- repository context
Related prompts
CI Failure Root Cause
Traces a continuous-integration failure through logs, configuration and recent changes before proposing a targeted repair.
Behavior Reconstruction
Reconstructs actual software behavior from code paths, tests, logs, data, and interfaces when documentation is incomplete or a regression's expected state is unclear.
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.
Issue Triage
Triages reported issues by reproducibility, impact, evidence, scope, dependencies, duplication, and next action so investigation effort goes to actionable defects first.
Spec Kit Bug Assessment
Assesses a reported defect against repository evidence, expected behavior, reproduction details, impact, and implementation context before a fix is attempted.