unit-test
Skill1 starsChanged 47 days agoGPL-3.0View on GitHub
单元测试工作流（生成 / 修复失败两类）。当用户要求"给如下代码生成单元测试"（覆盖主要逻辑分支与关键边界、可运行可通过、遵循项目现有测试规范与风格），或给出失败的单元测试执行结果要求"保证这些单元测试可以通过"时使用——修复失败类默认只改代码、不自行执行测试，改完交用户执行验证；生成类须验证可运行；不为变绿而弱化断言、删用例或改正确预期。即使未明确说"用 skill"，只要涉及单元测试的编写或修复就应使用。缺陷根因定位与生产代码修复用 bug-fix；从需求分析到落地的完整开发流程（单测只是其中一步）用 feature-dev；结构性改造与重构用 refactor。
13 other projects use a version of this.
Adopted by
Most recently taken up by
- neomjs/neo-agent-skillstheir own version, first seen Nov 8, 2026
- eyssette/js-templatetheir own version, first seen Nov 1, 2026
- kudeerliu48-web/CloseCodetheir own version, first seen Nov 1, 2026
- DongDuong2001/pudo-code-systemtheir own version, first seen Oct 13, 2026
- ivyfan-toowell/IvyClawtheir own version, first seen Oct 13, 2026
- phatysddev/skillstheir own version, first seen Oct 9, 2026
Used with
Projects with it also use e2e-test.
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.
WhatIfWeDigDeeperSkille2e-test
Create Playwright e2e tests for features in isolated worktree
Also in 4 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- xtermjs/xterm.js★ 21ksame name
- oprogramadorreal/optimus-claude★ 75same name
- ivyfan-toowell/IvyClaw★ 66same name
- johnqtcg/awesome-skills★ 30same name
- kudeerliu48-web/CloseCode★ 14same name
- neomjs/neo-agent-skills★ 11same name
- phatysddev/skills★ 8same name
- DongDuong2001/pudo-code-system★ 5same name
- kevinaimonster/skill-hub★ 4same name
- moveju112/skill_verify★ 1same name
3 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 repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- app-packagingSkill
- bug-fixSkill
- check-rule-extractSkill
- code-optimizeSkill
- code-reviewSkill
- comment-supplementSkill
- commit-createSkill
- db-querySkill
- doc-syncSkill
- feature-devSkill
- frontend-error-diagnoseSkill
- git-clean-branchesSkill
- git-history-rewriteSkill
- git-rollbackSkill
- git-worktreeSkill
- i18n-transformSkill
- log-diagnoseSkill
- module-batchSkill
- mr-createSkill
- nas-disk-diagnosticSkill
- opencode-batchSkill
- project-explainSkill
- refactorSkill
- repo-initSkill
- session-summarySkill
- skill-routerSkill
- spec-routeSkill
- task-commanderSkill
The file
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.