Vibe Coding · 课时

保留、修复还是拒绝

决定保留哪些内容，并要求改进其他内容

第 4 / 4 课13 个步骤

保留、修复还是拒绝 是 CoddyKit 上的免费 Vibe Coding 课时。这是第 4 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Vibe Coding 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Vibe Coding 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

The Decision That Makes You a Builder

You've read the AI's code and spotted possible issues. Now comes the part that actually ships products: deciding what to do about it.

Every chunk of AI code lands in one of three buckets: Keep it, Fix it, or Reject it. Making that call quickly and confidently is the core review skill.

This lesson gives you a simple framework so you never just blindly hit 'Accept All' again.

The Three Buckets

Here's the whole framework in one view:

Keep: it does what you asked, you understand it, no obvious risks. Accept it.
Fix: it's close but has a bug, a missing case, or messy bits. Ask AI to adjust it.
Reject: it's wrong-headed, overcomplicated, or doesn't match your goal. Throw it out and re-prompt.

Most code is 'Keep' or 'Fix'. Reject is rarer but powerful — don't be afraid to use it.

When to KEEP

Keep code when all three are true:

It does what you asked when you run or trace it.
You understand it enough to change it later.
You don't see obvious bugs or risks from your bug scan.

The function below is clean, named well, and does exactly one clear thing. This is a confident Keep.

function formatPrice(amount) {
  return '$' + amount.toFixed(2);
}

console.log(formatPrice(9.5));   // $9.50
console.log(formatPrice(12));    // $12.00

When to FIX

Fix when the code is mostly right but has a specific flaw you can name. You're not starting over — you're steering.

This code works for normal input but crashes on an empty cart. That's a clear Fix: keep the structure, patch the gap.

function cartTotal(items) {
  return items.reduce((sum, i) => sum + i.price, 0) / items.length;
  // bug: average not total, and crashes on empty cart
}

console.log(cartTotal([{ price: 4 }, { price: 6 }])); // 5, not 10!

How to Ask for a Fix

Good fixes come from specific requests. Don't say 'make it better' — name the exact problem so AI doesn't rewrite the whole thing or wander off.

Point at the precise issue, like this:

Fix two specific bugs in cartTotal, keep everything else the same:

1. It divides by length — I want the TOTAL, not the average.
2. It crashes on an empty cart — return 0 instead.

Show only the corrected function.

When to REJECT

Reject and re-prompt when fixing would be more work than restarting. Red flags for rejection:

It solves the wrong problem entirely.
It's a tangled mess you can't follow.
It uses invented libraries or fake functions.
It quietly ignored a key requirement you stated.

Rejecting isn't failure — it's faster than patching something broken at its core. In Cursor or Claude Code, just don't accept the diff and re-prompt.

Rejecting Well: Re-Prompt with Lessons

When you reject, don't just say 'try again' — tell the AI what went wrong so the next attempt is better, not the same.

Fold your finding into a sharper prompt:

That version doesn't work for me. Problems:

- It sorted oldest-first; I need NEWEST first.
- It imported a package that doesn't exist.
- It's way more complex than this needs to be.

Start over: simplest possible solution, newest-first, only built-in JavaScript, and explain your approach in one sentence first.

Small Chunks Make Decisions Easy

The secret to fast Keep/Fix/Reject calls: review in small pieces.

If you let AI write 200 lines at once, your only options are 'accept the whole mess' or 'reject everything.' But if you build one function at a time, each decision is tiny and clear.

Prompt in steps: 'First just the function to fetch data. Show me, I'll review, then we'll add the display.' Small chunks = confident reviews.

Trust Your Gut, Then Verify

If something feels off — too complex, too clever, doesn't quite match what you pictured — that instinct is worth listening to.

You don't have to prove it's broken to ask for better. A quick 'this feels overcomplicated, can you simplify?' costs nothing and often improves the code a lot.

You're the decision-maker. The AI proposes; you dispose. Comfortable saying 'no, again' is a superpower.

A Worked Example

Let's apply the framework to one real chunk. You asked AI for a function that returns the most recent post. It hands you this:

Trace it: it sorts by date but oldest-first, then grabs index 0 — so it returns the oldest post, the opposite of your goal. The structure is fine, the bug is specific and nameable.

Verdict: Fix. Keep the shape, just flip the sort. You'd reject only if it were tangled or solving the wrong task entirely.

function latestPost(posts) {
  const sorted = posts.sort((a, b) => a.date - b.date); // oldest first!
  return sorted[0]; // returns the OLDEST, not the latest
}
// Fix: sort newest-first (b.date - a.date), and guard empty list

Your Keep / Fix / Reject Checklist

Run this for every chunk of AI code:

Does it match my goal? If no → Fix or Reject.
Do I understand it? If no → ask to explain, then Fix or Reject.
Any bugs or risks? If yes → Fix.
Is it a tangled mess or wrong-headed? If yes → Reject and re-prompt.
All clear? → Keep, and move on.

This loop, on small chunks, is how reliable apps get built with AI.

Quick Check

AI generates a function that's mostly correct but crashes on an empty list and computes an average when you wanted a total. What's the right call?

在交互式课程中回答

Recap: Keep, Fix, or Reject

The decision framework you now own:

Keep when it matches your goal, you understand it, and it's risk-free.
Fix when it's close — name the exact bug and ask AI to patch just that.
Reject when it's wrong-headed or tangled; re-prompt with what went wrong.
Review small chunks so every decision stays easy and clear.
Trust your gut — you're the decision-maker; the AI proposes, you dispose.

You've now learned to review, read, debug-spot, and decide on AI code. That's the discipline that makes vibe coding ship real, working products.

免费开始

用 AI 导师学习 JavaScript — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 25
课程: 100

免费开始学习查看完整课程

常见问题解答

「保留、修复还是拒绝」课时是免费的吗？

是的 — 「保留、修复还是拒绝」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Vibe Coding 课程的其余内容，请升级到 CoddyKit PRO。 Vibe Coding 课程共包含 4 节课。

「保留、修复还是拒绝」这节课中我会学到什么？

决定保留哪些内容，并要求改进其他内容你通过在浏览器中直接运行的动手代码来练习 Vibe Coding，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Vibe Coding 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Vibe Coding 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 4 节课，共 4 节。

「保留、修复还是拒绝」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Vibe Coding 课中编写并运行代码吗？

能。每节 Vibe Coding 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Vibe Coding