t-demo-run
Run a single demo E2E test file, diagnose failures, dispatch fixes to agents, and re-run until pass.
Profile →npx skills add timzaak/web-dev-skills --skill t-demo-run --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 单文件 Demo 测试运行与修复 运行时边界统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md` 单文件运行与修复闭环统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/demo-run-repair-contract.md` ## 目标 - 先对一个测试文件整体执行。 - 整体失败时，再按用例粒度顺序执行。 - 单个用例失败时先诊断，再分发到对应 agent 修复。 - 修复后必须执行相关后端/前端补测，不能只跑 Demo。 - 输出可恢复的任务状态与机器可解析结果。 ## 使用方式 ```bash /t-demo-run demo/e2e/<role>/<scenario>.e2e.ts ``` ## 执行流程 - 校验参数：测试文件必须存在且扩展名为 `.e2e.ts`。 - 按 `dem
What does the t-demo-run skill do?
Run a single demo E2E test file, diagnose failures, dispatch fixes to agents, and re-run until pass.
How do I install it?
Run `npx skills add timzaak/web-dev-skills --skill t-demo-run --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From timzaak/web-dev-skills, a repository with 55 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.