docs(prompts): enhance debug prompt with ADO MCP pipeline tools and diagnostic report#457
Merged
Merged
Conversation
…iagnostic report Rework the debug-ado-agentic-workflow.md prompt to: - Add Azure DevOps MCP prerequisites section advising users to set up the @azure-devops/mcp pipelines toolset in their IDE/agent context - Introduce MCP-first automated investigation flow using pipeline tools (get_build_definitions, get_builds, get_build_status, get_build_log, get_build_log_by_id, get_build_changes) to find and analyze failing builds without manual log copy-paste - Add failure classification table mapping timeline records to stage-specific diagnosis sections - Add last-successful-build comparison as first-class regression path - Add standardized diagnostic report template with summary, evidence, environment, analysis, and root cause sections - Make GitHub issue filing mandatory as the final action (priority: GitHub MCP > gh CLI > raw markdown + link) - Scope the agent to investigation and reporting only — no fix proposals - Preserve all existing Stage 1/2/3 diagnosis content as-is - Keep manual fallback flow for when MCP is unavailable Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Enhances
prompts/debug-ado-agentic-workflow.md— the prompt loaded by the init-agent dispatcher when users need help debugging a failing ado-aw pipeline. The prompt now leverages Azure DevOps MCP pipeline tools for automated investigation and produces a standardized diagnostic report filed as a GitHub issue.Changes
New: Azure DevOps MCP prerequisites section
@azure-devops/mcpwith thepipelinestoolset in their IDE/agent context (NOT the pipeline frontmatter)get_build_definitions,get_builds,get_build_status,get_build_log,get_build_log_by_id,get_build_changesNew: MCP-first automated investigation flow (Steps 1–6)
ghCLI → raw markdown + linkNew: Failure classification table
Maps timeline records to stage-specific diagnosis sections (Setup, Agent infrastructure, MCPG, Agent runtime, Detection, Execution, Teardown, resource/auth issues).
New: Standardized diagnostic report template
Semi-rigid markdown template with: summary (pipeline info, failing step, confidence), evidence (sanitized logs, timeline, changes since last success), environment details, analysis, root cause, and issue metadata.
Scoping: Investigation and reporting only
Preserved