- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill pr-quiz -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill pr-quiz -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill pr-quiz -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill pr-quiz -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/MiniMax-AI/mcode-stack/tree/HEAD/stacks/jiachen/skills/pr-quizFrom the publisher
The quiz asks the author of a PR (on GitLab, a merge request) a few questions about their own change. The author ticks an answer in the PR, may read code while answering, and can open the answer key right after. The quiz never blocks a merge, so a question is worth asking only if a reviewer would want the author to have thought it through.
Each question probes one dimension:
design-intent: why the change does it this way and not another way;impact-surface: which callers, flows or stored data it affects;boundary: empty values, concurrency, ordering, repeated calls, old data;failure-mode: what happens when a step fails, times out or is retried, and how it degrades or rolls back.At least half of the questions are design-intent or failure-mode.
The correct answer follows from the code and the diff. Do not ask about intent the code cannot show.
No memory questions: never ask which file, function or variable changed, or anything the author could copy from the diff.
Give 3 to 5 options. Exactly one is correct. Each wrong option is a mistake a hurried author would plausibly make: a missed error branch, a forgotten second caller, two similar concepts mixed up. No absurd options.
Keep the options alike in length and detail. The correct option must not be the longest.
The author reads the quiz between other comments on the PR. Write each question the way a teammate asks at your desk, in the language the prompt asks for, and follow the section below for that language. In both languages a question uses at most one code name, in backticks, and only when there is no plain name for the thing.
Bad, a dense stem full of code names, and an option that gives a reason:
When the mobile NoteEditor flushes the drafts that the user wrote while offline through syncQueue.flush, and the SyncWorker has already started but the lastSyncedAt field of the current notebook has not been written yet, what does the header at the top of the editor render at this point?
- Falls back to rendering the local draftCache because its isDirty flag starts as true
Good rewrite of the same question:
A draft written offline needs to sync, but this notebook has never synced. What does the user see?
- The draft, updated after the sync
- Nothing until the sync finishes
- A sync error and a retry button
More rewrites:
The pipeline drops a question whose stem is longer than 45 words, has more than 2 code names, uses "at this point" or "at this moment", or opens with a "When", "While" or "Once" clause longer than 8 words, and a question with an option longer than 20 words, with more than 1 code name, or with a reason in it. It also drops a question that asks which file, function, method, variable, class or line, or what something is called. Stay well inside these limits.
Write the question in Simplified Chinese.
Bad, a dense stem full of code names, and an option that gives a reason:
手机端 NoteEditor 通过 syncQueue.flush 提交用户离线时写下的草稿,SyncWorker 已经启动但当前笔记本的 lastSyncedAt 字段还没写入,此时编辑器顶部呈现回执怎样?
- 回退为本地 draftCache 呈现,因为它的 isDirty 初始为 true
Good rewrite of the same question:
离线时写的草稿要同步上去,但这个笔记本还从没同步过。用户这时会看到什么?
- 先显示草稿,同步完再更新
- 先不显示,等同步完再显示
- 提示同步失败,让用户重试
More rewrites:
The pipeline drops a question whose stem is longer than 100 characters, has more than 2 code names, uses 此时 or opens with 当……时, and a question with an option longer than 45 characters, with more than 1 code name, or with a reason in it. Stay well inside these limits.
dimension: one of the four dimensions above.prompt: the stem.options: the option texts without letters. The pipeline adds the letters and shuffles the order.answer_index: the zero-based index of the correct option in options.explanation: why the correct option is right and the main wrong ones are wrong, in two or three plain sentences. It is shown after the author answers. Refer to options by their content, never by letter or position, because the order changes.evidence: up to three changed places that support the answer, each a path and a new-side line.Write multiple-choice questions that check whether a PR's author understands their change. Use only when the MCode Review pipeline asks for an author quiz.
---name: pr-quizdescription: Write multiple-choice questions that check whether a PR's author understands their change. Use only when the…---# stacks/jiachen/skills/pr-quiz/SKILL.mdFAQ
Download stacks/jiachen/skills/pr-quiz/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/MiniMax-AI/mcode-stack.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.