Guide Maestro's Linear issue/task journeys using exact team and issue identities, source-scoped controls, state mappings, and repository PR linkage.
中文简介正在准备中。当前显示原文说明。
安装前可以查看交给 AI 代理的指令内容。
Read maestro-integrations and orchestra-cli. Use the selected project's configured Linear connection; GitHub login does not authenticate Linear. Keep Linear workspace/team identity, issue UUID, display identifier, and issue URL separate from the Orchestra project/task IDs. Never send the linear: storage prefix as an API-native issue UUID.
The adapter reads a configured team key from connection metadata (legacy configurations may store it in endpoint) and maps workflow state types. Creation resolves that key to exactly one team UUID. Returned issues must confirm the native team before the registry binds the local Orchestra project. Do not assume a human team key is a UUID. Examine authenticated results and GraphQL errors even with HTTP 200.
Creation, assignment, state transitions, and PR attachment are distinct operations. Creation can send native assignee, workflow-state and priority values, but provider/runtime metadata is not established by a hosted issue response. Inspect the returned task and receipt rather than assuming every requested field was applied. If shared control reports unknown creation or missing scope, inspect that same team's inventory before retrying. Never create a duplicate in SQLite to hide a Linear failure. Reads currently return a bounded first page; do not claim a complete team inventory.
Use only advertised shared controls for task mutations. Guarded hosted queue/assignment support must be established by the executable and adapter; a generic Linear update method is not atomic admission. Preserve the user's existing authorization, but do not invent an unavailable command.
A Linear issue URL is not a PR link. Read the task's exact persisted PR linkage and use the matching repository provider skill to inspect the linked PR. Missing PR linkage is unknown/absent; mentioning an issue identifier in a branch is not linkage verification. Review and Done reconciliation remain separate from provider workflow-state mapping.
Connection setup belongs in Orchestra's tracker settings using the existing account/token mechanism; do not put keys in skills or global provider config. Linear's API guidance distinguishes personal keys from OAuth and requires checking GraphQL errors and team IDs. No configured connection means access is not established.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示原文说明。
Guide Maestro's Azure Boards and Repos task/PR identity and connection requirements while identifying Orchestra's currently unavailable Azure DevOps tracker operations.
中文简介正在准备中。当前显示原文说明。
Use GitHub repository issues and pull requests for Maestro task journeys, preserving Orchestra project identity, source routing, and exact PR linkage.
中文简介正在准备中。当前显示原文说明。