ado-bugs

Update Azure DevOps bugs by routing findings to System Info or comments.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/klemensms/mcp-consultant-tools --skill ado-bugs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ado-bugs
Source: https://github.com/klemensms/mcp-consultant-tools/tree/main/.claude/skills/ado-bugs
Command: npx skills add https://github.com/klemensms/mcp-consultant-tools --skill ado-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update Azure DevOps bugs with investigation findings, routing content to the System Info field when empty or adding a detailed comment when data already exists.

Core Features & Use Cases

  • Route investigation findings to the System Info field if it is empty.
  • Add formatted HTML findings as a comment when System Info already contains data.
  • Provide templates and guidance for consistent, traceable bug investigations.
  • Push changes via MCP server to ensure traceability and versioning.

Quick Start

Fetch the ADO bug by number and apply your investigation findings using the MCP workflow.

Frequently Asked Questions about ado-bugs

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

FAQPage Schema
How do I update Azure DevOps bugs with investigation findings?

To update Azure DevOps bugs, you fetch the work item by number and apply investigation findings via an MCP server workflow, routing content to the System Info field or as a formatted comment. This ensures changes are traceable and versioned.

How does routing work when adding investigation comments to ADO bug work items?

Routing logic directs investigation findings to the System Info field when it is empty. If System Info already contains data, the workflow adds a detailed HTML-formatted comment instead, preventing data overwrites on existing bug work items.

Does this workflow support HTML formatted content and links in ADO bug comments?

Yes, the workflow supports HTML-formatted content and links. It uses built-in HTML templates for both the System Info field updates and comments, ensuring investigation findings are structured consistently across Azure DevOps bug items.

What is the best way to automate adding system info to an Azure DevOps bug?

Automating Azure DevOps bug updates is best handled through a deterministic MCP server workflow. It fetches the bug by number and automatically routes findings to System Info, applying HTML templates for consistent, traceable documentation.

When should I not use the System Info field for bug investigation findings in ADO?

You should not use the System Info field when it already contains data. The workflow's routing logic prevents overwriting existing information, automatically redirecting new HTML investigation findings to a detailed comment on the bug work item instead.