Codex 嚴謹 diff 審查官:正確性、簡化、安全三軌過濾
讓 Codex 對你的 git diff 做一次有紀律的 code review:分三軌(正確性 bug/可簡化重用/安全)逐項列出,每個發現都標信心等級、給可貼的修正,並明確說「沒問題就說沒問題」,不無病呻吟。
把 PR 丟給 Codex 前先讓它自我審查。三軌過濾(正確性 / 簡化重用 / 安全),每個發現都帶信心等級+可直接貼的 patch,沒問題就明說沒問題——不是那種「整體看起來不錯」的廢話 review。
[ Log in to see the full prompt ]Sign up free to see the full prompt, copy it, save it, and join the discussion. Free content unlocks on login; Pro content is a separate subscription.
何時用:提交 PR 前、或請人 review 前,先讓 Codex 自己過一遍,省 reviewer 時間。為何有效:① 強迫它先 `git diff` 抓真實 diff(不是憑空評論),② 三軌分開跑避免「只看正確性、漏掉安全」,③ 信心等級+可貼 patch 讓你能快速採納或駁回,④ 明確允許「沒問題就說沒問題」破解 AI 愛無中生有湊發現的毛病。技巧:在 Codex 用 `codex exec --sandbox read-only "<貼上此 prompt>"` 跑成唯讀審查最安全;{{FOCUS_AREAS}} 留空它就以正確性為重,填「並發安全」「SQL 注入」可聚焦。Claude Code 直接貼進對話即可。
[TRACK A] [CONFIDENCE: high] src/cart.ts:42 What: applyDiscount 在 items 為空陣列時回傳 NaN Why it matters: 空購物車結帳會把 NaN 寫進訂單金額,下游付款端會拋錯 Fix: const subtotal = items.reduce((a, i) => a + i.price, 0); if (items.length === 0) return 0; [TRACK B] [CONFIDENCE: medium] src/cart.ts:55 What: 手寫的 round-to-2 與既有 utils/money.ts 的 toCents() 重複 Why it matters: 兩套四捨五入邏輯會在邊界分歧(0.005) Fix: import { toCents } from '../utils/money' Track C: no issues found VERDICT: merge-after-fixes。先修 src/cart.ts:42 的空陣列 NaN,這會直接影響結帳。
Suno Engineer's Mindset: 4 Steps to a Song That Doesn't Sound Like AI
A studio engineer's breakdown of Suno's fatal weaknesses (fried vocals, high-frequency artifacts), plus a 4-step DAW workflow and a Suno Studio cleanup prompt.
5 Claude Weekly Workflows That Stuck After 6 Months
Proposal generator / meeting processor / content repurposer / Friday review / shutdown reset — out of 40 I tried, only these 5 survived, each saving 30+ minutes per run.