council 是做什麼的？
運行一個由不同模型組成的子代理委員會，從多個角度探討同一問題，比較發現，並產生最終建議。當使用者要求委員會、第二意見、多個代理/模型評估一個問題、平行調查、紅隊/藍隊比較，或在競爭的技術方法之間做決定時，請使用此技能。
運行一個由不同模型組成的子代理委員會，從多個角度探討同一問題，比較發現，並產生最終建議。當使用者要求委員會、第二意見、多個代理/模型評估一個問題、平行調查、紅隊/藍隊比較，或在競爭的技術方法之間做決定時，請使用此技能。
這是一個名為「warpdotdev/council」的技能，用於建立一個由多個不同AI模型驅動的子代理委員會。它能讓開發者從多種角度平行調查同一個問題，模擬類似於紅隊/藍隊的對抗性評估、專家評議或尋求第二意見的場景。此技能支援多種AI平台，如Claude Code、Coder、Codex等。其工作方式是：首先建立多個子代理，每個子代理使用不同的模型（例如Claude、GPT、Gemini等），並賦予它們獨特的分析視角（例如安全性、效能、可維護性）；然後，每個子代理獨立調查問題並產生初步報告；最後，一個協調代理會比較這些報告，識別共識與衝突，並生成一份包含具體建議的最終綜合報告。這項技能特別適合用於評估複雜的技術決策、發現架構問題、或確保解決方案在多個維度上都經過嚴格審查。
npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/councilInstalled? Explore more 生產力與協作 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
運行一個由不同模型組成的子代理委員會，從多個角度探討同一問題，比較發現，並產生最終建議。當使用者要求委員會、第二意見、多個代理/模型評估一個問題、平行調查、紅隊/藍隊比較，或在競爭的技術方法之間做決定時，請使用此技能。
This repo contains 16 individual skills — each has its own dedicated page.
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.
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.
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.
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.
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.
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.
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.
Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence, and report reproduction findings. Use when investigating a specific interactive or visual bug from an issue, ticket, support report, or prompt.
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.
Walk users through PR review comments, fetching and displaying them first when needed, collect per-comment response decisions, apply requested fixes, and preview GitHub replies and resolutions before posting. Use when responding to PR review comments on the current branch.
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.
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.
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.
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.
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.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.