菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/NMDSdevopsServiceAdm/DataEngineering --skill new-ticket命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
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 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`.
Use when writing a new unit test in this repo, or migrating an existing test off unittest. Encodes the repo's dataclass+parametrize pattern, naming conventions, mocking rules, and test-data storage rules from STYLEGUIDE.md.
| name | new-ticket |
| description | 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. |
git status must be clean before switching branches — if not, stop and flag it rather than discarding anything.main. If not currently on main, confirm before switching.Ask two short questions, one at a time (see CLAUDE.md's Output style):
Don't try to gather full requirements here — that's what Plan Mode does next.
<trello-number>-<short-description>, slug hyphenated and truncated to fit the repo's 16-character limit (see "Environment & workflow" in CLAUDE.md). Create and check out the branch from latest main.
Call EnterPlanMode and let Claude Code's normal phased workflow (Explore → Design → Review → Final Plan → ExitPlanMode) do the deeper requirements interview and produce the plan. Don't build a separate SPEC format — the plan file is the SPEC.
Implement, then use commit-push (repeatedly, per logical change) and open-pr (once, at the end) to finish the cycle. There's no automatic memory save at any point — only save something to memory if it looks genuinely useful, and ask first.