Menú
Detect which tests are affected by recent code changes. Use when the user wants to know what tests to run after making changes.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
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.
Detect what changed and build only the necessary target. Use when the user says "build smart", "build inteligente", or wants an optimized build.
| name | affected-tests |
| description | Detect which tests are affected by recent code changes. Use when the user wants to know what tests to run after making changes. |
| user-invocable | true |
| argument-hint | [--run] [--base HEAD~1] |
Use the mcp__tml__project_affected-tests MCP tool.
Parse $ARGUMENTS:
true if --run or run is specified (automatically run affected tests)--base is specified (default: "HEAD")true if --verbose or verbose is specifiedCall mcp__tml__project_affected-tests with extracted parameters.
Report which test directories are affected and optionally their test results.