warpdotdev · Agent Skills
出典を確認した実質的な文書を持つ Skill が 29 件あります。カードを開くと原文、パッケージ内容、導入方法を確認できます。
write-tech-spec
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.
- 1時間の導入数
- 8
- GitHub Stars
- 712
- 更新日
- 11月11日
skill-doctor
Grades agent skills by scoring agent conversations for efficiency, code quality, procedure compliance, and verbosity, then drafts concrete skill edits and a shareable report. Use when the user wants their agent setup graded from real conversation history, or asks which of their installed skills are actually working.
- 1時間の導入数
- 3
- GitHub Stars
- 718
- 更新日
- 11月11日
council
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.
- 1時間の導入数
- 2
- GitHub Stars
- 718
- 更新日
- 11月11日
respond-to-pr-comments-in-blocklist
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.
- 1時間の導入数
- 2
- GitHub Stars
- 718
- 更新日
- 11月11日
write-feature-docs
Draft a complete documentation page for a new Warp feature from its PRODUCT.md and/or TECH.md spec. Use when an engineer has written a spec and needs to produce a first-pass MDX draft for the warpdotdev/docs repo. Also handles features without specs by researching the codebase first. Invoke this skill whenever an engineer mentions writing docs for a feature, drafting a docs page, creating feature documentation, starting the eng-docs workflow, or converting a spec into documentation. Requires an
- 1時間の導入数
- 2
- GitHub Stars
- 718
- 更新日
- 11月11日