免费在 GitHub 公开中文介绍

decide

逐项比较设计或实现方案，说明背景和选项并记录决定；也可按逻辑变更分步讲解已完成的代码，并汇总批准和修改意见。

原文查看原文说明

Walk the user through design or implementation decisions one at a time, or review completed code one change at a time. Use when the user says "walk me through each decision", "let's decide together", "help me work through these choices", "walk me through what you did", or "QA step by step". Present concise context, mutually exclusive options, log each answer, and finish with a summary.

ParadevAI/Paradev星标 15,724(GitHub 15,724 + cccskills 0)

实测评分未实测

查看安装方法

适用场景

逐项比较设计方案
讨论并记录实现决策
分步检查已完成的代码
整理批准意见和修改要求

中文介绍

功能

此技能会逐项提出设计或实现方面的决策，并记录选择结果。它会检查相关代码，整理出问题、不一致之处和需要决定的事项，再根据依赖关系和影响确定顺序。每项决策都包含具体背景、选择带来的利弊，以及两个到四个互不重复的选项。最后会把各项选择汇总成表格。

适用场景

当多个设计方案难以一次决定，或希望与智能体讨论实现方向时，可以逐项作出选择。此技能也能检查已经完成的代码；对于提交记录或拉取请求，会按逻辑变更单元拆分，并结合实际代码、文件名和行号逐项说明。

使用示例

“请和我逐项讨论并决定这些设计选择。”
“按顺序讲解这个拉取请求的变更，每一步都等我确认。”

注意事项

讨论设计方案时不会编写实现代码。未经明确批准，不会丢弃已有编辑或用户编写的内容。如果可以使用交互式提问工具，会使用该工具；仓库指定了交互方式时，则按其要求操作。检查代码时会等待每一步的回复，并记录批准结果和修改要求。

本介绍由 AI（OpenAI Codex）根据公开的 SKILL.md 撰写。准确的规格请查看下方原文。

文档检查

AI 根据 SKILL.md 的内容检查了需要注意的操作和使用前提。评分只依据实际运行的结果（实测对比）。

安全性发送数据、删除文件、执行命令等是否有说明: A良好未经批准不会丢弃编辑内容，检查时会等待回复并记录意见。
安装难易度所需工具和 API 密钥是否少且有说明: A良好资料未列出所需的外部工具、密钥或服务。

不计入评分。由 AI（OpenAI Codex）于 2026年10月29日评估。仅供参考，安装前请同时查看原文。

如果您认为评估有误，请申请复核

包含的文件（2）

SKILL.md2.7 KB
agents/openai.yaml196 B

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Decide

Prepare

Before a design walkthrough, inspect the relevant code and record concrete bugs, inconsistencies, and decision points in plans/<YYYYMMDD>-<topic>.md or the appropriate app-scoped plans/ directory. Preserve existing edits; never discard speculative or user-authored work without explicit approval.

Order decisions by dependency and leverage, not document order.

Decision walkthrough

For each decision:

Show ## Decision N: <title>.
Give two to four sentences of context grounded in real files or functions.
State the trade-off in one sentence.
Ask exactly one interactive question with two to four mutually exclusive options.
- Use ask_user when available. In Codex Plan mode, use request_user_input when that is the exposed interactive question tool.
- Never substitute a plain-text question when repository instructions require an interactive overlay.
- Keep labels to five words or fewer.
- Put the recommendation first and suffix its label with (Recommended).
- Explain each option and its trade-off in one sentence.
- Do not add an Other option when the client adds one automatically.
After the answer, write Logged: <decision>. and continue.

If the user acknowledges an issue without choosing, log the recommended choice and say they can correct the assumption.

At the end, provide a | # | Decision | Choice | table and offer to turn the audit into an implementation plan. Do not write implementation code during the decision walkthrough.

QA walkthrough

Use this mode when the user wants to review existing code step by step.

Identify the review unit: a commit, staged diff, PR, or explicit file set.
Break it into logical steps in dependency order.
Show one step per turn with:
- ## Step N: <title>
- One or two sentences explaining what changed and why
- A focused real-code excerpt with file and line references
- One interactive verdict question: Looks good, next step (Recommended), Push back, change this, and, only for non-trivial code, Pause, explain more
Wait for the verdict before showing the next step.
Log approvals, collect requested changes, and finish with a | # | Step | Verdict | table.

If a step reveals a genuine design fork, pause the QA walkthrough and offer to switch to decision mode for that fork.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能