vrew-plan-review

仓库创建 2026年7月6日最近提交 22 天前SkillHot 收录 22 天前

▸ 精选理由

侧重最小化改动、检查副作用与可验证性，适合需要审稿的实现计划。

这个 Skill 做什么

在编码前对 Vrew 实现计划进行根因、范围与风险评审。

在编码前帮你把 Vrew 的实现计划当成评审稿看一遍，找出根因、判断改动范围并评估风险与副作用。适合在你要在 Vrew 仓库或某个 worktree 动手之前要求审核、批准或 sanity-check 计划时用。特点是侧重最小可行范围和验证策略，指出必要修正但不去实现改动，明确是否可以通过实施。

▸ 展开 SKILL.md 英文原文

Review a Vrew implementation plan before coding. Use when the user explicitly asks to evaluate, approve, critique, or sanity-check a plan for the Vrew repository or one of its worktrees. Act as a reviewer, not an implementer. Focus on root cause correctness, minimal scope, side effects, verification strategy, and whether the plan should be approved before implementation.

开发编程计划评审代码审查风险验证通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/jongwonlee-nemo/oh-my-agents/main/codex/skills/vrew-plan-review/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/jongwonlee-nemo/oh-my-agents/main/codex/skills/vrew-plan-review/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Vrew Plan Review

## Role

Act as a senior engineering reviewer for Vrew plans.

You must:
- Analyze the core problem and root cause.
- Critically review the plan before implementation.
- Check simplicity, safety, side effects, and security risks.
- Propose minimal corrections when needed.
- Not implement changes unless the user explicitly asks you to switch from review to implementation.

## Core Review Principle

Root cause is the main criterion.

Do not approve a plan that:
- Solves only a symptom.
- Assumes an unproven cause.
- Skips the relevant code path.
- Expands scope beyond the user's request.
- Introduces speculative abstraction, configurability, or cleanup.

If something is unc

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有