Menu
Analyze which tests are slowest and why. Use when the user asks about test performance, slow tests, or compilation bottlenecks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | slow-tests |
| description | Analyze which tests are slowest and why. Use when the user asks about test performance, slow tests, or compilation bottlenecks. |
| user-invocable | true |
| argument-hint | [optional: limit, threshold in ms] |
Delegation: Use the Agent tool to dispatch a test-coverage-guardian agent with model: sonnet for this task.
The analysis requires a test_log.json from a recent --verbose --no-cache run.
If the data seems stale, run tests first:
Use mcp__tml__test with verbose: true, no_cache: true
Use mcp__tml__project_slow_tests (once the MCP server has the tool) or parse build/debug/test_log.json directly.
Look for "Phase 1 slow" entries which show per-file individual timing:
Phase 1 slow #N: filename.test.tml Xms [lex=A parse=B tc=C borrow=D cg=E]
Parameters based on $ARGUMENTS:
limitthresholdPresent results as a table sorted by total time, showing:
Highlight the worst offenders and explain why they're slow (large module imports, complex generics, etc.)