菜单
Meta-skill: choose which of the other five test-loop skills to invoke first, based on the user's description of the current state of their project. Use when a user says something like "I want to add tests to this project" or "this project has no CI" and the right entry point is not obvious.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Install the closed test loop into a fresh project. Copies the pre-commit hook, the CI workflow, the render script, the drift check script, the failure classifier, and the knowledge-base templates, then prepares the drill handoff that verifies the loop reacts.
Flag public symbols in the project's source tree that are not documented in the project's knowledge base. Use this before committing, in CI, or whenever a public API surface changes and you want to know whether the knowledge base has gone stale.
Verify the closed test loop actually reacts by injecting one intentionally failing test, running each of the five loop tools, and recording the result. Use after init-loop and after any change to a loop tool.
Group failing tests by naming convention so a real assertion failure is not hidden among tests that exist to verify a system rejects something. Use after running the test suite and before reading the report.
Turn a test runner's raw log into a Markdown report plus a structured JSON summary. Embeds the failure classification so a reader can see the failing tests, the run summary, and the failure-class counts on one page.
| name | test-loop-bootstrap |
| description | Meta-skill: choose which of the other five test-loop skills to invoke first, based on the user's description of the current state of their project. Use when a user says something like "I want to add tests to this project" or "this project has no CI" and the right entry point is not obvious. |
| metadata | {"type":"meta","language":"any","inputs":"user's free-form description of project state","outputs":"a single next-skill recommendation"} |
Pick the right next skill. The five other skills are pieces of one loop; this skill is the door.
When a user asks for help with testing, CI, or quality on a project and it is not obvious which of the five concrete skills to start with.
If you already know the user wants, say, drift detection, call drift-check directly. Do not use this meta-skill as an indirection layer.
A free-form description of where the project is now. Examples:
Q1: Does the project have at least one of:
- a pre-commit hook calling scripts/check_drift.sh
- a CI workflow calling swift test / pytest / etc.
- a docs/knowledge/ directory
--> If no: start with [init-loop]
--> If yes: continue to Q2
Q2: Did something just change in the public API (a new struct, function,
class, or trait)?
--> If yes: run [drift-check] now
--> If no: continue to Q3
Q3: Did the test suite just run, and did it produce at least one
failure?
--> If yes: run [failure-classify], then [report-render]
--> If no: continue to Q4
Q4: Have you (or anyone on the team) edited the loop tools
(scripts/*.sh, scripts/*.py, .githooks/*, .github/workflows/*)
in the last week?
--> If yes: run [drill] to verify the loop still reacts
--> If no: continue to Q5
Q5: When is the last time [drill] was run?
--> > 30 days: run [drill] as a regression check
--> <= 30 days: stop. The loop is healthy. No skill needed.
One of:
[init-loop][drift-check][failure-classify] + [report-render][drill]In addition, the skill should briefly state why it chose what it chose, so the user can override.