review-learning-content

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Review Exercode learning content

审查 Exercode 学习内容

  1. Read the applicable authoring skill and its linked references before reviewing:
    • generate-course-materials for courses, lecture materials, and embedded questions.
    • generate-judge-problems for Judge v2 problems.
    • generate-judge-contest for contests and their problem sets.
  2. Check the learning content for:
    • factual accuracy, using authoritative primary sources for material claims that are uncertain or important;
    • consistency with the request, surrounding materials, stated prerequisites, and target difficulty;
    • clear, unambiguous Japanese, correct terminology, spelling, Markdown, examples, and expected results;
    • questions that have exactly the intended answer and can be answered from the question as written;
    • code examples that are complete, runnable, and consistent with their explanations;
    • courses whose learning objectives include writing, modifying, or executing code provide course-scoped Judge problems at meaningful checkpoints, rather than relying only on embedded questions or complete examples;
    • every runtime and third-party dependency required by Judge problem files is declared reproducibly in the repository.
  3. For each embedded question, independently answer the question from its prompt and options before reading
    answerIndex
    ,
    answerIndices
    ,
    answerPattern
    ,
    modelAnswer
    ,
    hint
    , or
    explanation
    . Then compare your answer with those fields and verify that the intended answer is unique, correct, and supported by the question as written.
  4. For each Judge problem, first read only its statement and prerequisite materials. Before reading model answers or expected outputs, independently derive a solution, expected example outputs, and important boundary cases. Then inspect the model answers, test cases, templates, and judge implementation and verify that:
    • the statement provides enough information to solve the problem uniquely;
    • constraints, examples, model answers, expected outputs, and judge behavior agree;
    • the intended solution uses only concepts available to the learner;
    • test cases cover meaningful boundaries and every model answer is accepted by the judge — run
      bunx exercode-problem judge model_answers/<languageId>
      from the problem directory (it applies the problem's custom
      judge.ts
      when present and the standard stdio judge otherwise; see generate-judge-problems/references/problem-format.md) and confirm the command exits 0, prints at least one
      TEST_CASE_RESULT
      line, and every printed line has the accepted decision code
      2000
      ;
    • starter templates do not pass every test case.
  5. Run the applicable course, problem, and contest validators as supporting evidence. Execute model answers, templates, and judges through the repository-declared runtimes and dependencies. Treat a Judge problem that succeeds only through a global installation, ad hoc download, or temporary dependency environment as a concern. Do not treat validator success as proof of factual, pedagogical, or writing quality.
  6. Verify every suspected concern before reporting it. Report only concerns with a concrete correctness or learning-quality impact, not preferences.
  1. 审查前,先阅读适用的创作 skill 及其关联参考资料:
    • 对于课程、讲义和嵌入式问题,阅读 generate-course-materials。
    • 对于 Judge v2 题目,阅读 generate-judge-problems。
    • 对于竞赛及其题集,阅读 generate-judge-contest。
  2. 检查学习内容是否存在以下问题:
    • 事实准确性;对于不确定或重要的内容主张,应使用权威的一手来源进行核实;
    • 是否与需求、周边材料、既定先修知识和目标难度保持一致;
    • 日文是否清晰、无歧义,术语、拼写、Markdown、示例和预期结果是否正确;
    • 问题是否恰好具有预期答案,并且可以仅根据题目本身作答;
    • 代码示例是否完整、可运行,并与相应说明保持一致;
    • 对于学习目标包含编写、修改或执行代码的课程,是否在有意义的学习检查点提供了课程范围内的 Judge 题目,而不是仅依赖嵌入式问题或完整示例;
    • Judge 题目文件所需的每项运行时和第三方依赖是否都以可复现的方式声明在仓库中。
  3. 对于每个嵌入式问题,在读取
    answerIndex
    、
    answerIndices
    、
    answerPattern
    、
    modelAnswer
    、
    hint
    或
    explanation
    之前,先根据题干和选项独立作答。然后将答案与这些字段进行比较,并确认预期答案唯一、正确且可由题目本身推导得出。
  4. 对于每个 Judge 题目,先只阅读其题面和先修材料。在读取模型答案或预期输出之前,独立推导出解答、预期示例输出和重要边界情况。随后检查模型答案、测试用例、模板和 Judge 实现,并确认:
    • 题面是否提供了足够的信息,以确保题目有唯一解;
    • 约束条件、示例、模型答案、预期输出和 Judge 行为是否一致;
    • 预期解法是否仅使用学习者已经掌握的概念;
    • 测试用例是否覆盖有意义的边界情况,并且 Judge 接受每个模型答案——在题目目录中运行
      bunx exercode-problem judge model_answers/<languageId>
      (存在题目自定义的
      judge.ts
      时会使用该文件,否则使用标准 stdio Judge;参见 generate-judge-problems/references/problem-format.md),并确认命令以状态码 0 退出、至少打印一行
      TEST_CASE_RESULT
      ,且每一行打印结果的接受决策码均为
      2000
      ;
    • 起始模板是否会通过所有测试用例。
  5. 运行适用的课程、题目和竞赛验证器,以其结果作为辅助证据。通过仓库声明的运行时和依赖执行模型答案、模板及 Judge。若某个 Judge 题目仅能通过全局安装、临时下载或临时依赖环境成功运行,则应将其视为一个问题。不得将验证器运行成功视为内容在事实、教学或写作质量方面正确的证明。
  6. 报告前,核实每项疑似问题。只报告会对正确性或学习质量产生具体影响的问题,不报告个人偏好。