菜单
Verify MDT's shipped Codex setup against the local workflow contract. Use when auditing Codex support, checking whether installed setup files still exist, validating Codex workflow coverage, or producing a readiness report without relying on CI or live model calls.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
How to use the Serena MCP server for token-efficient code navigation, symbol analysis, and targeted editing. Use this skill whenever Serena tools are available (mcp__serena__* tools appear in your tool list), when exploring unfamiliar codebases, before editing any file larger than ~100 lines, when finding all callers of a function, or when you need to understand a module without reading it whole. ALWAYS prefer Serena's symbolic tools over raw Read calls for TypeScript, JavaScript, Python, or any language with LSP support — it is almost always faster and cheaper.
Use context-mode tools (ctx_execute, ctx_execute_file) instead of Bash/cat when processing large outputs. Triggers: "analyze logs", "summarize output", "process data", "parse JSON", "filter results", "extract errors", "check build output", "analyze dependencies", "process API response", "large file analysis", "page snapshot", "browser snapshot", "DOM structure", "inspect page", "accessibility tree", "Playwright snapshot", "run tests", "test output", "coverage report", "git log", "recent commits", "diff between branches", "list containers", "pod status", "disk usage", "fetch docs", "API reference", "index documentation", "call API", "check response", "query results", "find TODOs", "count lines", "codebase statistics", "security audit", "outdated packages", "dependency tree", "cloud resources", "CI/CD output". Also triggers on ANY MCP tool output that may exceed 20 lines.
Instinct-based learning system for Codex. Manual-first: explicit capture and analysis baseline, with optional background observer.
Keep repository documentation current, accurate, well-placed, and easy to follow for both humans and LLMs. Use when auditing doc drift, correcting stale claims, deciding where docs belong, or validating documentation quality before a commit.
Instinct-based learning system that adapts to the environment: hooks-passive observation for Claude/Cursor, explicit capture for hook-free tools. Single unified surface for all tools.
Keep repository documentation current, accurate, well-placed, and easy to follow for both humans and LLMs. Use when auditing doc drift, correcting stale claims, deciding where docs belong, or validating documentation quality before a commit.
| name | mdt-dev-verify |
| description | Verify MDT's shipped Codex setup against the local workflow contract. Use when auditing Codex support, checking whether installed setup files still exist, validating Codex workflow coverage, or producing a readiness report without relying on CI or live model calls. |
Use this skill when auditing MDT's local Codex adapter, validating documented Codex workflow coverage, or producing a Codex readiness report without relying on CI or live model calls.
In MDT repo mode, read these first:
docs/tools/capability-matrix.mddocs/tools/workflow-matrix.mdscripts/lib/tool-workflow-contract.jsIn installed global tool mode:
~/.codex/skills/mdt-dev-verify/SKILL.md~/.codex/mdt/scripts/lib/tool-workflow-contract.js~/.codex/ plus ~/.codex/mdt/ as the install surfacemdt verify tool-setups.mdt dev smoke tool-setups.mdt dev smoke workflows --tool codex.docs/testing/manual-verification/codex.md for the required real Codex session check.node ~/.codex/mdt/scripts/mdt.js dev smoke tool-setups.node ~/.codex/mdt/scripts/mdt.js dev smoke workflows --tool codex.docs/testing/manual-verification/codex.md for the required real Codex session check.SKIP.