评审一个列表接口
一个分页列表接口。改一个参数，你能看到谁的数据？
Copy the prompt, then pick a model. It plays the interviewer and asks you through it scene by scene instead of handing you the answer.
On a phone with the app installed, the system opens the app directly. Links cannot open external apps inside WeChat — open it in a browser first.
The copied text ends with the answer key the model grades you against. Don't read it yourself first — working it out on your own is the point.
这一份不接受名词。你说「这里有越权」，它会说：把那个 HTTP 请求写出来，参数填成什么，你会看到谁的数据。 写不出请求的，记成背的。
其中有一条是这批题里最值钱的知识点之一：参数化查询挡不住它。为什么挡不住、那该用什么，第三幕会问到底。
第四幕还有一问值得先想想：你的修法是写在这个函数里，还是有一层统一的地方 —— 下一个人写新接口时会不会又忘一次。
Mostly planted here
This prompt in the repo (the answer key is at the end of that file — you'll see it)
Have you done this one?
Sign in to mark this one as practised — next time you come back you'll see when you did it.
Notes from people who did this one
How to use this
The material is ours: a few dozen lines that look like working code, with about ten defects planted in order of severity. So this series needs nothing from you — open one and start.
The stance is interrogation: no spoilers, no praise, and being unable to answer is a normal outcome. Say "there is a race here" and it will not let it go — it wants two columns of timeline and the size of the damage.
How to start
- Pick one, open it, copy the prompt.
- Paste it into a fresh, empty chat; it will paste the code back to you as-is.
- Read it yourself and name every problem you find — in the first scene it will not interrupt or hint. Say "that is all" when you are done.
Four commands you can call out any time
跳过Move on to the next scene提示Give me a direction, not the answer直说吧Give the full answer for this point, then keep pressing on the cost复盘Jump straight to the wrap-up card
The wrap-up is a number
A find rate: how many you caught, out of how many, and how many were false alarms. Plus one uglier number — how many of the ones you missed are in the top severity band (loses money, leaks data, takes the service down). That number is worth more than the score.
Three traps
- The answer key at the end is that list of defects. Do not read it first — once you have, this drill is spent.
- Do not report naming or style. What counts here is whether money is lost or data leaks; style reports are recorded as false alarms.
- The moment it praises you, point it back at the "do not praise me" rule. Feeling validated drowns out "what did I miss".
Start with the transfer one — it has the densest set of defects. If you write API endpoints all day, go straight to the list endpoint: its broken access control and sort-parameter injection are the easiest to find a twin of in your own code. Whichever you do, go grep your own repo afterwards — the real output is those three take-away checks.
Sign in to write a note.