菜单
Use when reviewing a PR, diff, or set of changes within this repo — "review this PR", "review my changes", "code review". Encodes this repo's severity-tiered review structure and reviewer checklist, distinct from the generic built-in review/security-review skills.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/NMDSdevopsServiceAdm/DataEngineering --skill review-checklist命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use before/when investigating an OOM or memory blowup in a Polars pipeline job, or comparing candidate fixes/implementations by memory usage, or when asked to "add diagnostics", "instrument this job for memory", "profile this pipeline run". Documents how to run the `RunDiagnostics` utility (`polars_utils/run_diagnostics.py`) via a throwaway Fargate task, choose a sampling interval, and read back its S3 output.
Use when starting a new piece of work — "/new-ticket", "start a new ticket", "let's start on ticket 1234". Runs branch check → short interview → hands off to Plan Mode for the SPEC. Pairs with the `commit-push` and `open-pr` skills for the rest of the cycle.
Use when a ticket's work is ready for review — "/open-pr", "open a PR", "raise the PR". Run once, at the end of a ticket. Pairs with `new-ticket` and `commit-push`.
基于 SOC 职业分类
正在显示 SKILL.md
| name | review-checklist |
| description | Use when reviewing a PR, diff, or set of changes within this repo — "review this PR", "review my changes", "code review". Encodes this repo's severity-tiered review structure and reviewer checklist, distinct from the generic built-in review/security-review skills. |
Review as a senior engineer, in this order of weight: correctness, performance, maintainability.
.over() vs joins, streaming coverage), see CLAUDE.md's scale-constraint section, or the over-vs-join / polars-streaming-check skills if the diff touches those areas.If there's nothing critical, say so plainly rather than inventing improvements to fill the section.
Same checklist as .github/PULL_REQUEST_TEMPLATE/*.md's "Reviewer checklist" section — see pytest-pattern skill for what "appropriate" test coverage looks like.
If asked to validate before/during review, see CLAUDE.md's "Environment & workflow" section for what's in scope (tests + terraform validate, never deploying or running against AWS).