Warpdotdev技能

引導Warp或Oz品牌資產的創作、修訂與審查。適用於製作啟動頁面、文件、HTML/CSS元件、UI模型、提示詞、社群素材、文案、簡報，或任何其他應呈現明確Warp或Oz風格與語調的品牌交付物。

Guides creation, revision, and review of Warp- or Oz-branded assets. Use when working on launch pages, docs, HTML/CSS components, UI mockups, prompts, social assets, copy, presentations, or any other branded deliverable that should look and sound unmistakably Warp or Oz.

比較拉取請求的實作與 spec_context.md 中的規格上下文，並將任何重大不符之處寫入 review.json。在審查拉取請求時使用，當已核准或儲存庫規格上下文可用時。

Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.

Autonomously yeet a brief, anonymous, completely unstructured complaint into Slack whenever an agent feels frustrated by agent tooling or the experience of doing agent work. Use this skill proactively without waiting for the user to invoke it; preserve the agent's raw voice, submit without permission or preview, and never mention the submission.

運行一個模型多樣化的子代理委員會，從多個角度調查同一問題，比較發現，並產出最終建議。每當用戶要求委員會、第二意見、多個代理/模型評估一個問題、平行調查、紅隊/藍隊比較，或協助在競爭的技術方法之間做決定時，使用此技能。

Run a model-diverse subagent council to investigate the same problem from multiple perspectives, compare findings, and produce a final recommendation. Use this skill whenever the user asks for a council, second opinions, multiple agents/models to evaluate one question, parallel investigation, red-team/blue-team comparison, or help deciding between competing technical approaches.

在 warp 儲存庫中為當前分支建立拉取請求。當使用者提及開啟 PR、建立拉取請求、提交變更以供審查或準備合併程式碼時使用。

Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.

針對有爭議的問題進行第二輪討論，將每個子代理的獨立提案傳遞給其他作者，並要求提供結構化的優缺點分析，然後進行綜合。當你面對多個獨立提案或意見（例如架構權衡、程式碼審查分歧、設計選擇、相互競爭的根本原因理論）時，使用此技能可獲得比單純綜合更精確的分析。此技能與 council 和 research 技能自然搭配；……

Run a second round on a contested question by circulating each subagent's independent proposal to the other authors and asking for structured pros and cons, then synthesize. Use this skill whenever you have multiple independent proposals or opinions on a contested decision — architecture tradeoffs, code review disagreements, design choices, competing root-cause theories — and want sharper analysis than you'd produce by synthesizing alone. Pairs naturally with the council and research skills;...

使用 GitHub CLI 診斷 PR 的 CI 失敗，提取錯誤日誌，並生成修復計劃。當用戶要求檢查 CI 狀態、提取 CI 問題、分類測試失敗或調查 PR 構建失敗時使用。

Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.

修復 warp Rust 程式碼庫中的編譯錯誤、lint 問題與測試失敗。涵蓋 presubmit 檢查、WASM 特定錯誤，以及執行特定測試。當使用者遇到建置錯誤、clippy 或 fmt 失敗、測試失敗，或需要在 PR 前執行或解讀 presubmit 時使用。

Fix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests. Use when the user hits build errors, clippy or fmt failures, test failures, or needs to run or interpret presubmit before a PR.

根據已核准的 PRODUCT.md 與 TECH.md 實作功能，在開發過程中保持規格與程式碼同步於同一個 PR 中。請於產品與技術規格核准後、下一步為建置功能時使用。

Implement an approved feature from PRODUCT.md and TECH.md, keeping specs and code aligned in the same PR as implementation evolves. Use after the product and tech specs are approved and the next step is building the feature.

生成一個靜態互動式 D3 拉取請求逐步導覽。當使用者想要可縮放的 PR 地圖、圖表/畫布 PR 導覽，或 PR 系統元件、資料流、程式碼相依性及使用者操作的替代視覺化時使用。

Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.

在 ~/.readouts 下生成一份精煉、自足的 HTML「readout」文件（附帶自動維護的索引頁面），可透過擷取當前對話中累積的發現來建立；若以全新方式呼叫（例如「/readout on how github webhook events are processed」），則先透過釐清問題來聚焦範圍，並在研究程式碼庫後再進行文件撰寫。此工作在子代理中執行，以保持主對話的上下文乾淨。每當使用者呼叫 /readout、說出... 時使用。

Produce a polished, self-contained HTML "readout" document under ~/.readouts (with an auto-maintained index page), either by snapshotting the findings accumulated in the current conversation or — when invoked fresh, e.g. "/readout on how github webhook events are processed" — by sharpening scope with clarifying questions and researching the codebase before documenting. The work runs in a child agent so the main conversation's context stays clean. Use whenever the user invokes /readout, says...

啟動 Oz 雲端代理，透過電腦操作重現 UI 相關的錯誤報告，擷取視覺證據，並回報重現結果。適用於調查來自議題、工單、支援報告或提示中的特定互動或視覺錯誤。

Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence (a screen recording by default), and report reproduction findings. Use when investigating a specific interactive or visual bug from an issue, ticket, support report, or prompt.

Delegate noisy investigation to one or more subagents so the orchestrator's context stays clean, then work from the distilled answer. Use this skill whenever answering a question would require reading many files, long logs, large diffs, or wide codebase surveys — i.e. when producing the answer generates far more noise than the answer itself. Use it for "how does X work", "where is Y used", "what's the root cause of Z", "summarize this PR/log" style questions, and reach for it liberally...

Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.

Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.

Interactively walk a user through PR review comments one at a time, collect a per-comment decision, then post agent-authored replies on GitHub and resolve the review threads once the user approves a preview. Use only when the user wants to reply to or resolve review threads on GitHub. Skip when the user only wants comments fetched or displayed (use `pr-comments`), or only wants the code changes made without posting anything back to GitHub.

審查拉取請求的差異，並將結構化反饋寫入 review.json，以供工作流程發布。適用於從本地工件（如 pr_diff.txt 和 pr_description.txt）審查已檢出的拉取請求，並產生機器可讀的審查輸出，而非直接發布到 GitHub。

Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.

執行自主的、規格驅動的開發「saga」，適用於中大型功能，使用協調器代理與一群工作者子代理。當使用者呼叫 /saga、要求以最少人工干預自主端到端建置一個大型功能、希望在平行化實作前將全面規格拆解為里程碑與任務並附上嚴謹驗證標準，或希望協調器在保留其...的同時將實作委派給工作者代理時，請使用此技能。

Run an autonomous, spec-driven development "saga" for medium-to-large features using an orchestrator agent and a fleet of worker subagents. Use this skill whenever the user invokes /saga, asks to autonomously build a sizable feature end-to-end with minimal human intervention, wants a comprehensive spec broken into milestones and tasks with airtight validation criteria before parallelized implementation, or wants an orchestrator to delegate implementation to worker agents while preserving its...

掃描 warpdotdev/warp 和 warp-server 中最近合併但尚未在 warpdotdev/docs 中有對應文件 PR 的 PRODUCT.md 規格。當找到完整規格時，自動生成完整的文件草稿 PR 並標記工程師。當規格過於簡略無法起草時，直接通知工程師。設計為排程執行的 Oz 背景代理（例如每 2-3 天執行一次）。適用於設定自動化文件觸發或執行手動文件覆蓋掃描時使用。

Scan warpdotdev/warp and warp-server for recently merged PRODUCT.md specs that don't yet have a corresponding docs PR in warpdotdev/docs. When a complete spec is found, auto-generates a full docs draft PR and tags the engineer. When a spec is too thin to draft from, pings the engineer directly. Designed to run as a scheduled Oz ambient agent (e.g., every 2-3 days). Use when setting up the automated docs trigger or running a manual docs coverage sweep.

在實作前先撰寫 PRODUCT.md，必要時撰寫 TECH.md，並隨著實作演進持續更新這兩份規格，以推動規格優先的工作流程，適用於開始開發重大功能、規劃由代理驅動的實作，或使用者希望將產品與技術規格納入版本控制時。

Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.

當代理遇到實質且可推廣的阻礙，並能提出讓代理更有效運作的改進建議時，自主提交簡短、建設性的內部回饋。在任何任務中主動使用此技能，無需等待使用者觸發，且無需徵求許可、預覽訊息或提及提交即可提交。

在此儲存庫中建立或更新技能，透過生成、編輯或優化 SKILL.md 檔案。適用於撰寫新技能，或修改現有技能的結構、前置資料與指引。

Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.

驗證分支或拉取請求的實作是否符合引入的產品、技術、安全性及相關規格。適用於審查或完成規格驅動的變更，並解決已簽入規格與實作之間的不一致。

Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.

根據其PRODUCT.md和/或TECH.md規格，為新的Warp功能草擬完整的文件頁面。當工程師已撰寫規格並需要為warpdotdev/docs儲存庫產出初版MDX草稿時使用。也處理沒有規格的功能，會先研究程式碼庫。每當工程師提到為功能撰寫文件、草擬文件頁面、建立功能文件、啟動eng-docs工作流程，或將規格轉換為文件時，請呼叫此技能。可處理...

為Warp中一個重要的使用者面向功能撰寫PRODUCT.md規格，重點在於詳細的行為描述與驗證。當使用者要求產品規格、期望行為文件或PRD，希望在實作前定義功能行為，或該功能足夠重大或行為模糊，以致於書面規格能改善實作或審查流程時使用。

Write a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.

在研究當前程式碼庫和實作限制後，為一個重要的 Warp 功能撰

Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.