warehouse-ux-pr-review

Lists, triages, and reviews pull requests in the TridentWarehouse-UX Azure DevOps repository.

Updated Jul 4, 2025
One-click install
npx skills add https://github.com/milespossing/nixdots --skill warehouse-ux-pr-review-milespossing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: warehouse-ux-pr-review
Source: https://github.com/milespossing/nixdots/tree/main/modules/agents/_skills/warehouse-ux-pr-review
Command: npx skills add https://github.com/milespossing/nixdots --skill warehouse-ux-pr-review-milespossing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Reviewing pull requests in the TridentWarehouse-UX Azure DevOps repo requires juggling MCP tool calls, authentication quirks, and consistent review standards. This Skill centralizes the repo constants, MCP tool usage, and a distilled review philosophy so listing, triaging, and reviewing PRs follows one repeatable workflow. ## Core Features & Use Cases - PR Listing and Triage: Query open, completed, or assigned PRs via the azure-devops MCP server and present them as a Markdown table with optional file and comment counts. - Structured PR Review: Fetch PR metadata and diffs, then generate candidate review comments grouped by file with severity tags, evidence links, and draft text based on a documented review philosophy. - Fallback Shell Scripts: Use az rest-based scripts (list-prs.sh, show-pr.sh) when the MCP server is unavailable, with non-interactive authentication checks. - Use Case: Ask "what PRs are waiting on me" to get a filtered table of active PRs where you are a reviewer, then say "review PR 1234" to receive candidate comments grounded in the repo's architectural rules. ## Quick Start Ask the assistant to list the open pull requests in the TridentWarehouse-UX repo or to review a specific PR by its ID.

Frequently Asked Questions about warehouse-ux-pr-review

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

FAQPage Schema
How do I list open pull requests in an Azure DevOps repo?▼

Use the mcp_ado_repo_list_pull_requests_by_repo tool with the repository ID and a status filter such as active. Results are presented as a Markdown table with ID, status, author, updated date, and title columns.

How do I review a pull request with the azure-devops MCP server?▼

Fetch metadata with mcp_ado_repo_get_pull_request_by_id and the diff with mcp_ado_repo_get_pull_request_changes using includeDiffs and includeLineContent. Then apply the review philosophy reference to produce candidate comments grouped by file.

What do I do when Azure DevOps authentication fails with a 401 error?▼

A 401 or token acquisition error means the local az login session expired. Run az login --tenant 72f988bf-86f1-41af-91ab-2d7cd011db47 in your own terminal, then retry the request; the skill does not retry automatically.

Can I use this without the azure-devops MCP server?▼

Yes, the scripts directory provides list-prs.sh and show-pr.sh which call the Azure DevOps REST API directly via az rest. They are slower due to Python startup per call but functionally equivalent to the MCP tools.

Does the skill post review comments to Azure DevOps automatically?▼

No, it only drafts candidate comments with severity tags and evidence for the user to review. Posting via mcp_ado_repo_create_pull_request_thread or voting happens only on an explicit user request.