omc-ado-triage

Azure DevOps triage aggregates work items, open PRs, pipeline health, and security alerts into a single prioritized overview. It reads connection settings from .omcp/config.json, queries relevant ADO surfaces in parallel, and outputs a structured summary with recommended actions.

An Azure DevOps project health overview surfaces untriaged items, active work, open PRs, pipeline failures, and security risk. The triage process queries all relevant ADO surfaces and presents an actionable summary with suggested next steps and guardrails for handling failures.

Yes, Azure DevOps triage requires a .omcp/config.json file to obtain your org, project, repo, and filters. The skill reads this configuration to establish connection settings and execute data queries across work items, PRs, pipelines, and security alerts.

Yes, Azure DevOps triage queries security alerts and pipeline health together. It executes data queries in parallel across all relevant ADO surfaces, providing visibility into security risk and pipeline failures alongside untriaged work items and open PRs.

An Azure DevOps triage summary includes untriaged items, active work, open PRs, pipeline health, and security risk. It provides a prioritized overview with recommended actions and guardrails for handling failures or alerts to help you determine next steps.

Automated triage handles Azure DevOps pipeline failures and security alerts by aggregating them into a structured overview with recommended actions. It applies guardrails for handling failures or alerts, ensuring you can quickly assess security risk and pipeline health.