Guide Maestro's Azure Boards and Repos task/PR identity and connection requirements while identifying Orchestra's currently unavailable Azure DevOps tracker operations.
中文简介正在准备中。当前显示原文说明。
安装前可以查看交给 AI 代理的指令内容。
Read maestro-integrations. Keep Azure organization, project, work item numeric ID, repository ID, and PR ID distinct from Orchestra project/task/workspace IDs. Work item URLs and Repos PR URLs identify different resources.
Orchestra currently has no Azure DevOps tracker adapter in its adapter factory. This skill does not add an account connection or enable issue/task commands. Do not silently route Azure work to GitHub/SQLite, select a different tracker, or report Azure Boards tasks as synchronized. Record the missing capability explicitly in the user's journey.
If an Azure tool or CLI is actually available and the user has authorized its use, validate its organization/project scope and read access before reporting access. Authentication setup belongs in the account/connection flow, never in skill text. Inspect tool help and use the installed version; this skill does not advertise Azure CLI commands that Orchestra has not provided.
The implementation journey is: configure a verified Azure connection, discover exact project/work item identity and process-specific states, provide source-scoped observation/create/assignment with durable receipts, preserve work item revision checks, bind a local execution/workspace separately, attach the exact Repos/GitHub PR URL, then verify review/head/checks before task-state reconciliation. These adapter and reconciliation steps remain unavailable until implemented and behaviorally verified.
For an existing local Orchestra task with Azure PR linkage, preserve the stored PR URL and identify the repository provider without claiming the task originated in Boards. No PR link means no observed linkage.
Primary reference: Azure DevOps Work Items API. Provider API documentation is a design input, not proof of a working Orchestra integration.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
中文简介正在准备中。当前显示原文说明。
Investigate stuck runs and execution failures by tracing Symphony and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.
中文简介正在准备中。当前显示原文说明。
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
中文简介正在准备中。当前显示原文说明。
Native Linear integration using internal tracker tools. Supports issue querying, state transitions, and audit logging.
中文简介正在准备中。当前显示原文说明。
Use GitHub repository issues and pull requests for Maestro task journeys, preserving Orchestra project identity, source routing, and exact PR linkage.
中文简介正在准备中。当前显示原文说明。
Route Maestro issue-to-task-to-PR work through Orchestra's configured GitHub, Linear, Jira, or Azure DevOps integration and report connection and workflow gaps.
中文简介正在准备中。当前显示原文说明。