What problem does it solve? Azure DevOps PR descriptions support only a subset of GitHub-flavored Markdown, and features like mermaid, KaTeX math, and in-table line breaks silently fail. This Skill tells you exactly which Markdown features work in ADO PR descriptions and comments, how to link work items, PRs, and users, and how to structure a clean PR write-up. ## Core Features & Use Cases - Support matrix: A verified table of which Markdown features render in PR descriptions versus wiki-only features to avoid. - Linking syntax: Correct shorthand for work items (#123, AB#123), cross-PR references (!456), user mentions, commits, branches, and builds. - Ready-to-fill templates: Six PR templates by change kind (feature, bug fix, refactor, revert, chore, draft) plus reusable snippets like screenshot rows and collapsible logs. - Use Case: You are migrating a GitHub PR body to Azure DevOps and need to convert task lists, collapsible sections, and AB# work-item links into syntax that actually renders in ADO. ## Quick Start Ask the assistant to draft an Azure DevOps PR description for your current diff using the appropriate template and linked work items.