Agents | Add Azure DevOps work item markdown formatting guide & PR feedback prompt#4253
Open
paulmedynski wants to merge 4 commits into
Open
Agents | Add Azure DevOps work item markdown formatting guide & PR feedback prompt#4253paulmedynski wants to merge 4 commits into
paulmedynski wants to merge 4 commits into
Conversation
paulmedynski
added
the
Area\Engineering
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new repository instruction guide documenting a safe, repeatable workflow for updating Azure DevOps work item descriptions to Markdown while preserving newline integrity, and links it from the agent guidance index.
Changes:
- Added a new instruction file under
.github/instructions/coveringaz restJSON-patch patterns and verification scripts forSystem.DescriptionMarkdown formatting. - Updated
AGENTS.mdto reference the new guide in the “Detailed Technical Instructions” table. - Minor formatting tweaks in
AGENTS.md(additional blank lines for readability).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
.github/instructions/ado-work-items-markdown.instructions.md |
New guide documenting Markdown formatting rules, safe update steps, and post-update verification checks for ADO work items. |
AGENTS.md |
Adds a link to the new ADO work item Markdown guide in the technical instructions table (plus minor spacing adjustments). |
mdaigle
previously approved these changes
May 5, 2026
paulmedynski
changed the title
auto-merge was automatically disabled
May 8, 2026 16:48
Pull request was converted to draft
- Create ado-work-items-markdown.instructions.md with safe patterns for markdown description updates - Document two-step conversion for changing field format without data loss - Include newline integrity checks and batch verification scripts - Update AGENTS.md to link new instruction guide for discoverability
- Tested it with this PRs comments.
paulmedynski
force-pushed
the
dev/paul/ado-instructions
branch
from
5fc9bec to
b67e3bb
Compare
paulmedynski
commented
May 29, 2026
Contributor
Author
paulmedynski
left a comment
paulmedynski
left a comment
There was a problem hiding this comment.
Submitting pending review
| ## Quick Start | ||
|
|
||
| ### Essential Context Files | ||
|
|
Contributor
Author
There was a problem hiding this comment.
Fixed linter errors in this file. I have another PR somewhere to introduce proper MarkDown linting configuration and checking.
paulmedynski
changed the title
Use file-based capture (pipe to file) instead of command substitution to preserve trailing newlines. Step 3 now uses jq --rawfile to read back the description byte-for-byte.
paulmedynski
force-pushed
the
dev/paul/ado-instructions
branch
from
b67e3bb to
97a05e7
Compare
cheenamalhotra
approved these changes
May 29, 2026
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
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.
Description
This PR adds comprehensive instructions for ensuring markdown content is properly formatted when creating or updating Azure DevOps work items, and a reusable prompt for reviewing PR feedback.
Changes
New file:
.github/instructions/ado-work-items-markdown.instructions.mdNew file:
.github/prompts/review-pr-feedback.prompt.mdghCLIUpdated:
AGENTS.mdContext
These instructions document the workflow discovered while updating 26 work items (4 stories + 22 tasks) for the pipeline implementation project. The patterns ensure:
The PR feedback prompt was developed and used to help work through this PRs feedback.