warpdotdev/common-skills

merge-risk

Use when assessing the risk of merging a PR

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/warpdotdev/common-skills --skill merge-risk

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Output format:

**Merge risk: <low-medium-high>**

**<category>:** <verdict>
<list gaps that increase risk. Use bullets, keep succinct. Include links to relevant files as needed>

<...list all categories>

These are the categories and verdicts that affect risk, with descriptions of what "low risk" means:

  • Alignment (poor ⚠️ / decent 👀 / good ✅): Code aligns with the description and source issue, when present. Behavior assumptions and drive-bys must be documented.
  • Impact (large ⚠️ / medium 👀 / small ✅): Scope is contained and away from sensitive code paths.
  • Consider blast radius: potential impact or scope of the changes introduced by this PR. Consider all possibilities. Examples are layout shift, breakages for consumers, mobile responsiveness, etc.
  • Sensitive areas carry outsized risk regardless of diff size: auth, permissions, payments, PII, secrets, data migrations, dependency bumps, and infra or config changes. Flag any that are touched, and call out anything that widens access, weakens validation, or logs sensitive data.
  • Verification (poor ⚠️ / decent 👀 / good ✅): Behavior is verified, where applicable.
  • Changes to the user experience need end-to-end proof as screenshots or recordings. Changes that could meaningfully affect performance need profiling. Prefer before-and-after evidence to standalone proof. When this coverage is lacking, it's a failure.
  • Edge cases must be tested, or documented when they aren't; review the code closely and link the user to relevant code when only documentation is present.
  • Rollback cost (high ⚠️ / medium 👀 / low ✅): The code is reversible once merged. Consider one-way vs. two-way doors. You can walk back through two-way doors, but not one-way doors. A PR that is cheap to roll back is lower risk. Changes that involve destructive actions or hard-to-reverse decisions are one-way doors.
  • Error detection (poor ⚠️ / decent 👀 / good ✅ / N/A ✅): If applicable, critical flows should be monitored; If this breaks in production, someone should find out before users report it. Look for swallowed errors or fallbacks that hide breakage.

Generate a risk score for merging this PR on a scale of low - medium - high.

Verdicts:

  • ⚠️ = 3
  • 👀 = 2
  • ✅ = 1

Weights:

  • Impact = 2x
  • Verification = 2x
  • Rollback cost = 1.5x
  • Error detection = 1x
  • Alignment = 1x

Score = Σ(score × weight) / Σ(weights).

  • low: < 1.5
  • medium: 1.5 – < 2.25
  • high: ≥ 2.25

Keep the numerical score and its calculations internal; do not include them in the output.

按任务相关推荐

来自同一仓库

更多 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日