菜单
Enumerate every test file in a codebase, extract test subjects and assertions, detect the test framework in use, and emit test-surface.yaml. Used by test-engineer.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/kapilvirenahuja/garura --skill map-test-surface命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Install Garura into a target project or repository so its skills, agents, and plays become discoverable by a host coding tool — Claude Code or the OpenAI Codex CLI. Reads this garura checkout's core/components and runs a per-tool ADAPTER that lays them down in the host's native shape: for claude, .claude/ skills + agents with model tiers resolved to Claude models; for codex, .agents/skills Agent Skills plus AGENTS.md and ~/.codex model/sandbox/approval profiles. Always writes a .garura/ tooling tree (config + STM scaffold) and copies shared memory to the machine-global ~/.garura, and records an install manifest so uninstall-garura can reverse exactly what was placed. Use when the user wants to install, set up, bootstrap, add, or enable Garura in another folder or repo for claude or codex — "install garura into X", "set up garura in this repo for codex", "bootstrap garura", "make codex see the garura skills". Takes the target path, an optional --tool, and an optional --scope (full = everything, the default; ha
Compile a deterministic "play" (a multi-step, gated workflow recipe) from an intent. Interviews for the intent triple, generates the expectation, identifies the skills, scripts, and agents the play needs, selects a workflow structure, generates evals, and emits a compiled play (a SKILL.md plus bundled scripts for its mechanical work). Use this whenever the user wants to create, build, compile, or review a play — or says "create a play", "new play", "compile this into a play", "play-creator", "turn this intent into a play", or "review my play for gaps" — even if they don't say the word "play" explicitly but are describing a repeatable, multi-step, checkpoint-gated workflow they want captured as a runnable recipe.
Modify an existing compiled play — change its goal, a constraint, a failure condition, a success scenario, a step, the workflow shape, or the agents/skills it uses — by editing the play's ICE source and recompiling, never by hand-patching the output into disagreement with its intent. This is the companion to play-creator (which makes new plays). Use this whenever the user wants to edit, change, modify, update, tweak, extend, or fix an existing play — or says "edit the play", "change this play", "add a constraint to the play", "the play needs a new failure condition / step / scenario", "play-editor", or "recompile the play after I changed its intent" — even if they don't say "play" outright but are clearly reshaping a workflow recipe that already exists.
基于 SOC 职业分类
正在显示 SKILL.md
| name | map-test-surface |
| description | Enumerate every test file in a codebase, extract test subjects and assertions, detect the test framework in use, and emit test-surface.yaml. Used by test-engineer. |
| user-invocable | false |
| model | sonnet |
| allowed-tools | Read, Write, Grep, Glob, Bash |
| deprecated | true |
| deprecated_note | #434 ProductOS realignment — superseded by the command model; retained for Phase E reference, not installed |
Model-invocable skill for mapping the test surface of a codebase.
Produce a complete inventory of existing tests: file locations, subjects (what they test), assertion counts, frameworks used. Emit test-surface.yaml — the basis for later blast-radius computation and coverage-gap analysis.
Previously authored inline by test-engineer.
| Field | Required | Description |
|---|---|---|
project_root | yes | Codebase root |
test_globs | optional | Override test-file globs (default auto-detect by language) |
output_base | yes | Directory to write test-surface.yaml |
Detect test framework(s). From config (pytest.ini, jest.config, go.sum, etc.) and file naming (*_test.py, *.test.ts, *_test.go, spec/ dirs).
Glob test files. Language-specific defaults; user override via test_globs.
Per file, extract:
it(...) / methodsassert, expect(, should)Aggregate. Total test count, assertion count, per-framework counts, subjects covered.
Emit test-surface.yaml:
project_root: "{project_root}"
generated_at: "{ISO-8601}"
frameworks: [ ... ]
totals:
test_files: {n}
test_functions: {n}
assertions: {n}
files:
- path: "{test file}"
framework: "{name}"
subjects: [ "{module/class/function under test}" ]
test_count: {n}
assertion_count: {n}
[ ]
[ ]
test_surface_path: "{output_base}/test-surface.yaml"
test_file_count: {n}
status: written