test
Skill88 starsChanged 20 days agoMITView on GitHub
执行项目完整测试流程(编译检查 + 单元测试)。 当需要运行测试或验证代码质量时使用。
186 other projects use a version of this.
Adopted by
Most recently taken up by
- br3eze-code/br3eze-codetheir own version, first seen Nov 16, 2026
- vericontext/vibeframetheir own version, first seen Nov 15, 2026
- TJaenichen/claude-code-harnesstheir own version, first seen Nov 15, 2026
- Renozoic-Foundry/forge-publictheir own version, first seen Nov 15, 2026
- nazmirket/skillstheir own version, first seen Nov 15, 2026
- RohiRIK/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
parcadeiSkillagentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +10 more from parcadei
Other versions186 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 186
- facebook/react★ 253ksame name
- react/react★ 252ksame name
- apache/skywalking★ 25ksame name
- livewire/livewire★ 24ksame name
- NVIDIA/TensorRT★ 13ksame name
- FalkorDB/FalkorDB★ 11ksame name
- FastLED/FastLED★ 7.5ksame name
- fleetdm/fleet★ 7.2ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
176 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-taskSkill
- archive-tasksSkill
- block-taskSkill
- cancel-taskSkill
- check-taskSkill
- close-codescanSkill
- close-dependabotSkill
- code-taskSkill
- commitSkill
- complete-manual-validationSkill
- complete-taskSkill
- create-prSkill
- create-release-noteSkill
- create-taskSkill
- entropy-checkSkill
- import-codescanSkill
- import-dependabotSkill
- import-issueSkill
- init-labelsSkill
- init-milestonesSkill
- plan-taskSkill
- post-releaseSkill
- refine-titleSkill
- releaseSkill
- restore-taskSkill
- review-analysisSkill
- review-codeSkill
- review-planSkill
- review-prSkill
- run-manual-validationSkill
- test-integrationSkill
- update-agent-infraSkill
- upgrade-dependencySkill
- watch-prSkill
The file
Files
执行测试
执行项目的完整测试流程,包括编译检查和单元测试。
1. 编译 / 类型检查
npm run typecheck项目测试脚本会先运行 npm run build,因此单独执行类型检查后无需在本步骤重复构建。
2. 运行测试(按层级选择)
测试层级是反馈速度优化;本项目按测试的可观察范围与运行成本选择对应层级。新增测试文件默认归入 full,确认足够快且足够核心后,再上调到 core 或 smoke。
fast smoke(参考目标 <10s)
npm run test:smoke:fast与 smoke 运行相同的 unit 测试范围,但跳过构建。仅用于代码修改后的内循环;完成一个实施步骤后仍须运行 smoke,以验证最新构建产物。
runner 默认使用 availableParallelism() * 2 个测试进程;需要固定并发时可设置 AGENT_INFRA_TEST_CONCURRENCY,例如 AGENT_INFRA_TEST_CONCURRENCY=4 npm run test:smoke:fast。
platform-smoke(跨平台边界)
npm run test:platform-smoke:fast运行从 unit 迁出的真实 CLI、git、shell 和子进程测试。该层在 Windows/macOS 上保留原有跨平台执行边界;完整 integration 测试仍由 test:core、test:integration 或 CI integration job 执行。
smoke(参考目标 <10s)
npm run test:smoke适用场景:
- code-task 的实施步骤完成后
- 仅断言项目结构、配置、模板契约
core(参考目标 <95s)
npm run test:core适用场景:
- pre-commit hook(自动调用)
- 写 code.md / code-r{N}.md 报告前的最终验证
- 推送 PR 前的本地把关
full(参考目标 <100s)
npm test适用场景:
- release / tag 前
- CI(unit-tests.yml)
- main 合并前的最终把关
full 层运行全部项目测试。npm test 使用通配匹配项目测试文件,新增的测试文件会自动归入 full,这是安全网。参考目标是反馈预算,不是 CI gate。
npm run test:coverage 只在 main push 的独立 CI job 中运行;覆盖率用于定位薄弱区域,不设置百分比门槛,也不阻塞合并。
3. 输出结果
报告测试结果摘要:
- 运行的总测试数
- 通过数量
- 失败数量(包含每个失败的详情)
- 测试覆盖率(如已配置)
失败处理
如果测试失败:
- 输出失败详情和建议的修复方向
- 在任务范围内且可诊断时,先检查证据并修复本次引入的问题,再运行相同测试验证;涉及范围外设计、用户数据冲突或必要授权时记录阻塞并继续独立工作。
后续步骤
测试通过后,建议提交变更:
渲染下一步前先读取
.agents/rules/next-step-output.md,仅为已选场景调用统一 helper,并将 stdout 填入{next-step-commands}。
使用 agent-infra-internal agent-client next-steps --skill commit 生成本场景的 {next-step-commands}。
下一步 - 提交代码:
{next-step-commands}Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

