菜单
Add a new configuration field, setting, or tunable — invoke when adding a knob to server.json, cli.json, community/, or enterprise/. Covers the Pydantic schema, the PEP 257 trailing docstring, config-samples, and tests; prevents ad-hoc os.environ reads and DEFAULT_FOO constants
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/deephaven/deephaven-mcp --skill config-field-add命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Add a new command to the dhcli CLI — invoke when adding or editing a verb under cli/_commands/. Wraps the click + Pattern B + structured-error + agents-manifest conventions; prevents the most common bugs (calling asyncio.run inline, printing errors to stderr, forgetting to update docs/CLI.md)
The content contract for dhcli CLI help — required sections, HelpSpec authoring, plain-text rendering rules, single-source output schema, and docs/CLI.md consistency — invoke when authoring or reviewing any command help, option help, or the agents manifest
Conventions for dhcli commands that wrap an MCP tool — wrapper categories, type scoping, path-flag locality (CLI-read vs server-side), and the wraps_tool drift contract — invoke when adding/editing a cli/_commands verb that fronts a tool; not for authoring MCP server tools (ref-mcp-module-organization)
基于 SOC 职业分类
正在显示 SKILL.md
| name | config-field-add |
| description | Add a new configuration field, setting, or tunable — invoke when adding a knob to server.json, cli.json, community/, or enterprise/. Covers the Pydantic schema, the PEP 257 trailing docstring, config-samples, and tests; prevents ad-hoc os.environ reads and DEFAULT_FOO constants |
Adding a configuration field is governed by the ref-configuration-conventions skill. Apply it and follow its add-a-tunable checklist — schema location, the field plus a PEP 257 trailing docstring, an attribute-access consumer, the four artifacts that move in lockstep, and tests — together with the design anti-patterns it catalogs (no ad-hoc os.environ / DEFAULT_FOO, the field-design pitfalls). This workflow adds the glue around that checklist:
Verify the field's docstring reached runtime. Pydantic harvests the trailing docstring into model_fields[name].description; confirm it before relying on it (tests/test_field_docs_contract.py fails otherwise):
uv run python -c "from <module> import <Model>; print(<Model>.model_fields['<field>'].description)"
Run run-precommit and tests-run-file on the changed test files.