warpdotdev/common-skills

scan-new-specs

DEPRECATED and retired as of 2026-08-20.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/warpdotdev/common-skills --skill scan-new-specs

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

scan-new-specs (deprecated)

Retired 2026-08-20. Do not invoke this skill and do not schedule it.

Its scheduled agent (0ITuF9vNJ1RiO00Szlm1fW) is paused and stays paused.

Why it was retired

The skill fired on spec merge, which happens before a feature ships. Two failures followed from that single design choice:

  • It drafted docs for unreleased and sometimes abandoned work. A merged spec is not a shipped feature. The agent had no evidence of what users had actually received, so pages were written for behavior that had not landed, or had landed differently, or never landed at all.
  • It treated every spec as a docs task. Nothing asked whether a change warranted documentation. Pure UI changes, small intuitive additions, and behind-the-scenes work all became draft PRs, and the docs repo accumulated unvetted content debt faster than anyone could review it.

What replaces it

The missing_docs skill in warpdotdev/docs, running in drift-watch mode. It differs in the two ways that matter:

  • Release-triggered. scripts/check_new_release.py gates each run on a new stable release, so the pipeline sees what actually shipped rather than what was planned. A daily schedule does per-release work.
  • Gated on worthiness. Every candidate is evaluated against .agents/references/docs-worthiness-criteria.md before anything is drafted, with a default of no docs and a requirement to name concrete evidence. Verdicts, including rejections, are recorded in references/changelog_decisions.md so nothing is re-litigated.

Anything genuinely worth documenting re-surfaces there once it ships.

If you were about to run this

  • Looking for docs gaps? Run missing_docs in drift-watch mode from the warpdotdev/docs repo.
  • You are an engineer who wants docs for your feature? Invoke write-feature-docs directly and interactively. It still works, and it still walks you through spec research and outline confirmation. It no longer runs headlessly.
  • Setting up a scheduled docs agent? Use missing_docs, not this. Scheduling this skill reintroduces exactly the flooding it was retired for.

Related skills

  • missing_docs (in warpdotdev/docs) — the release-triggered, worthiness-gated replacement
  • write-feature-docs — still supported for direct, interactive use by an engineer
同じリポジトリから

関連する Skills

すべての Skills
warpdotdev
コミュニティ

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日
warpdotdev
コミュニティ

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日
warpdotdev
コミュニティ

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日
warpdotdev
コミュニティ

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日