菜单
Run TML tests using the MCP test tool. Use when the user says "test", "roda os testes", "run tests", or wants to verify changes. Supports running specific test files, filtered tests, specific suites, or the full suite.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | test |
| description | Run TML tests using the MCP test tool. Use when the user says "test", "roda os testes", "run tests", or wants to verify changes. Supports running specific test files, filtered tests, specific suites, or the full suite. |
| user-invocable | true |
| argument-hint | optional suite name, file path, filter, no-cache, fast |
Delegation: For large test runs or test analysis, use the Agent tool to dispatch a tester agent with model: sonnet. For quick single-file tests, execute directly.
Use the mcp__tml__test MCP tool for ALL test operations. NEVER use Bash to run tml.exe test.
Based on $ARGUMENTS:
verbose: truecore/str, std/json, compiler/compiler): Run that suite with suite parameterlib/std/tests/net/ip.test.tml): Run that specific file with path parameterlib/std/tests/net/): Run all tests in that directory with path parametercollections): Run matching tests with filter parameterno_cache: true to force recompilationfail_fast: true to stop on first failureSuite names follow the pattern <lib>/<module>:
core/str, core/fmt, core/num, core/iter, core/ops, core/alloc, ...std/json, std/collections, std/crypto, std/io, std/sync, std/net, ...compiler/compiler, compiler/runtime, compiler/borrow, ...Use --list-suites via CLI to see all available suites.
Call mcp__tml__test with appropriate parameters:
suite: Suite group name (e.g., "core/str", "std/json") — preferred for module-level testingpath: Specific file or directoryfilter: Test name filter (file path substring)verbose: Always true for useful outputno_cache: Force full recompilation when requestedfail_fast: Stop on first failure when requestedstructured: Use for machine-readable results (total/passed/failed/failures)When verifying changes to a specific module, ALWAYS use suite parameter instead of running the full test suite. This is dramatically faster:
suite="core/str" → ~3s (241 tests)suite="std/json" → ~4s (153 tests)Only run the full suite when explicitly asked or when changes are cross-cutting.
After tests complete:
Detect and fix documentation violations across C++ compiler and TML library code. Scans for missing ///, undocumented public items, wrong comment styles, and auto-fixes using parallel agents. Use when the user says "fix docs", "audit docs", "documenta", "corrige docs", or wants to improve documentation coverage.
Deep knowledge of TML compiler internals. Inject before working on compiler C++ code. Maps the full pipeline with key functions, types, and cross-subsystem boundaries.
Deep knowledge of TML standard library structure, module dependencies, key types, and C runtime mapping. Inject before working on library code.
Detect which tests are affected by recent code changes. Use when the user wants to know what tests to run after making changes.
List build artifacts with sizes and ages. Use when the user asks about build outputs, compiled binaries, or disk usage.
Build the TML compiler from C++ sources. Use when the user says "build", "compila", "rebuild", or needs to recompile the compiler after C++ changes.