Use when requirements exist and a technical design is needed before implementation begins
中文简介正在准备中。当前显示原文说明。
Use EVERY TIME you need to run tests, verify tests pass, or check for regressions. ALWAYS use this instead of running eldev directly.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Run ./run-tests.sh (in this skill's directory) to execute tests. The script handles all noise filtering and outputs only a clean summary.
.claude/skills/test/run-tests.sh [ARGUMENT]
Parse the ARGUMENTS line and pass it through:
| Argument | What it does |
|---|---|
(none) / all | Full suite |
test/unit/foo-test.el | Single file |
unit / integration / acceptance | Category |
If the argument contains / but no .el (looks like a test name, e.g. stuck-sa-filter/cancelled-project-task-skipped):
deftest <name> in test/ to find the filerun-tests.shThe script returns one of:
Success: PASS: 1195 tests in 18.4s
Failure: Summary line + full failure/error details (test name, expected/actual, file:line)
Unexpected: Last 30 lines of raw output
Report the script output verbatim. Do not add commentary unless the user asks.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Use when requirements exist and a technical design is needed before implementation begins
中文简介正在准备中。当前显示原文说明。
Use when a new feature request, bug report, or work request needs requirements defined before implementation
中文简介正在准备中。当前显示原文说明。
Use when a design exists and it's time to break it into tasks and execute with subagent dispatch and review
中文简介正在准备中。当前显示原文说明。
Use when implementation is complete and you want to verify quality through adversarial testing that writes code and provides evidence
中文简介正在准备中。当前显示原文说明。
Use when code quality needs improvement after implementation, without changing behavior
中文简介正在准备中。当前显示原文说明。
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
中文简介正在准备中。当前显示原文说明。