@needfspeed/skills-library 0.1.0

package/CATALOG.md

@@ -0,0 +1,19 @@
+# 资料目录
+
+## Skills
+
+| 领域 | 名称 | 入口 | 用途 |
+| --- | --- | --- | --- |
+| Java | java-mockito-tests | `skills/java/java-mockito-tests/SKILL.md` | JMockit 到 Mockito 迁移、JDK 17 兼容和测试验证 |
+
+## Docs
+
+当前暂无独立文档。与某个 skill 强相关的资料放在该 skill 的 `references/` 中。
+
+## Examples
+
+当前暂无示例项目。
+
+## Templates
+
+当前暂无模板。

package/README.md

@@ -0,0 +1,46 @@
+# @needfspeed/skills-library
+
+个人维护的 AI skills 与工程资料集合。资料按用途分类，安装后可从 `node_modules/@needfspeed/skills-library` 读取。
+
+## 安装
+
+```bash
+npm install --save-dev @needfspeed/skills-library
+```
+
+## 目录
+
+```text
+skills/       可直接复制到 AI 工具技能目录的完整 skill
+docs/         按技术领域分类的独立文档
+examples/     示例项目与用法
+templates/    可复用模板
+CATALOG.md    全部资料索引
+```
+
+当前收录 `java-mockito-tests`，用于将 Java 项目的 JMockit 单元测试迁移到兼容 JDK 17 的 Mockito 实现。
+
+## 使用 skill
+
+把完整 skill 目录复制到目标 AI 工具支持的技能目录。例如 Codex：
+
+```powershell
+Copy-Item -Recurse node_modules/@needfspeed/skills-library/skills/java/java-mockito-tests $env:USERPROFILE/.codex/skills/
+```
+
+通义灵码若使用不同的技能目录，复制同一完整目录到其要求的位置；请保留 `SKILL.md`、`agents/` 和 `references/` 的相对结构。
+
+## 维护约定
+
+- 每个 skill 使用 `skills/<领域>/<skill-name>/`。
+- 独立知识文档使用 `docs/<领域>/`，不要复制 skill 内部 reference。
+- 示例按领域放入 `examples/<领域>/`。
+- 模板放入 `templates/<类型>/`。
+- 新增资料时同步更新 `CATALOG.md` 并提升包版本。
+
+发布前运行：
+
+```bash
+npm run check
+npm run pack:check
+```

package/docs/java/README.md

@@ -0,0 +1,3 @@
+# Java 文档
+
+独立 Java 工程资料放在本目录。与某项 skill 的执行规则和迁移映射紧密相关的内容，应放在该 skill 自己的 `references/` 中，避免两份内容漂移。

package/examples/java/README.md

@@ -0,0 +1,3 @@
+# Java 示例
+
+需要完整可运行示例时，按主题建立子目录，并在子目录中说明 Java、构建工具和测试框架版本。

package/package.json

@@ -0,0 +1,31 @@
+{
+  "name": "@needfspeed/skills-library",
+  "version": "0.1.0",
+  "description": "A categorized collection of reusable AI skills and engineering reference materials.",
+  "keywords": [
+    "codex-skill",
+    "documentation",
+    "java",
+    "mockito"
+  ],
+  "license": "UNLICENSED",
+  "private": false,
+  "files": [
+    "skills/",
+    "docs/",
+    "examples/",
+    "templates/",
+    "CATALOG.md"
+  ],
+  "scripts": {
+    "check": "node scripts/check-package.mjs",
+    "pack:check": "npm pack --dry-run"
+  },
+  "publishConfig": {
+    "access": "public",
+    "registry": "https://registry.npmjs.org/"
+  },
+  "engines": {
+    "node": ">=18"
+  }
+}

package/skills/java/java-mockito-tests/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: java-mockito-tests
+description: Create, repair, or migrate Java unit tests with Mockito, especially when replacing JMockit for JDK 17 compatibility. Use for JUnit 4 or 5 projects; do not change production behavior merely to make tests pass.
+---
+
+# Java Mockito Tests
+
+Work from the project's existing build, Java, JUnit, Mockito, and Spring versions. Inspect the relevant production code and tests before editing. Preserve the project's current test style unless migration requires a focused change.
+
+## Workflow
+
+1. Identify the actual test runner, build modules, test source sets, and commands used by the repository.
+2. Find JMockit dependencies, imports, annotations, `-javaagent` configuration, and test patterns in the affected scope.
+3. Convert behavior in small groups while preserving assertions and the scenario each test protects.
+4. Run the narrowest affected test first, then the owning module's full test task.
+5. Confirm the test count is non-zero and that the intended test class appears in the output. A successful build with skipped or undiscovered tests is not evidence of success.
+6. After the affected scope passes, remove JMockit configuration only when no remaining tests depend on it.
+
+For concrete mappings from JMockit APIs to Mockito and ordinary Java techniques, read [references/jmockit-to-mockito.md](references/jmockit-to-mockito.md).
+
+## Framework choices
+
+- For JUnit 5, prefer `@ExtendWith(MockitoExtension.class)` when extension-based initialization fits the existing project.
+- For JUnit 4, prefer `@RunWith(MockitoJUnitRunner.class)` or a scoped `MockitoRule`. Use `MockitoAnnotations.openMocks(this)` only when runner or extension integration is unsuitable, and close the returned resource.
+- Use the Mockito capabilities supported by the project's existing dependency line. Add or upgrade dependencies only when the required behavior is unavailable and the change is compatible with the repository.
+- Prefer dependency injection and observable behavior. Use static or construction mocking only for legacy seams that cannot reasonably be supplied as dependencies within the task.
+- Use Spring test facilities only when the test actually needs a Spring context. Keep ordinary unit tests context-free.
+
+## Correctness constraints
+
+- Do not delete, weaken, or broadly replace meaningful assertions just to obtain a passing build.
+- Do not make all mocks lenient. Remove unnecessary stubs or apply leniency only to the specific shared stub whose use legitimately varies.
+- Do not mock the class under test. Use a spy only when partial real behavior is part of the scenario and a smaller seam is unavailable.
+- Avoid deep stubs unless the external API shape makes them unavoidable; prefer explicit collaborators and values.
+- Match arguments precisely enough to preserve the test's intent. Do not replace meaningful values with `any()` indiscriminately.
+- Use `verify` for meaningful interactions, not for every implementation detail. Prefer state or return-value assertions where those express the contract.
+- Do not introduce sleeps for asynchronous behavior when the project has a deterministic synchronization mechanism.
+- Never report migration complete while JMockit imports, dependencies, plugin arguments, or `-javaagent` settings remain in the claimed scope.
+
+## JDK 17 checks
+
+Check build plugins and test runtime options as well as source compatibility. Remove JMockit agents only after confirming they are unused. Treat `--add-opens` and similar module flags as evidence of a compatibility workaround: keep flags still required by other libraries and remove only those proven to belong solely to the retired setup.
+
+Report which tests ran, the command used, any remaining JMockit usage, and any compatibility limitation that could not be resolved in the requested scope.

package/skills/java/java-mockito-tests/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Java Mockito Tests"
+  short_description: "迁移并维护兼容 JDK 17 的 Mockito 单元测试"
+  default_prompt: "Use $java-mockito-tests to migrate these Java tests from JMockit to Mockito and verify that the intended tests run."

package/skills/java/java-mockito-tests/references/jmockit-to-mockito.md

@@ -0,0 +1,118 @@
+# JMockit 到 Mockito 迁移参考
+
+只在迁移或审查 JMockit 测试时读取本文件。先确认项目的 JUnit 和 Mockito 版本，再选择可用 API。
+
+## 常见映射
+
+| JMockit | Mockito 或 Java 替代方式 |
+| --- | --- |
+| `@Mocked` | `@Mock`，或局部 `mock(Type.class)` |
+| `@Injectable` | 显式创建 mock 并传入被测对象；适合时使用 `@InjectMocks` |
+| `@Tested` | 显式构造被测对象；简单构造器注入可使用 `@InjectMocks` |
+| `new Expectations() {{ ... }}` | `when(...).thenReturn(...)`、`thenThrow(...)` 或 `doReturn/throw(...)` |
+| `new Verifications() {{ ... }}` | `verify(...)`、`times(...)`、`never()`、`InOrder` |
+| `result = value` | `thenReturn(value)` |
+| `result = exception` | `thenThrow(exception)` |
+| `times/minTimes/maxTimes` | `times/atLeast/atMost` |
+| `withAny/withEqual/withCapture` | `any/eq/ArgumentCaptor` |
+| `MockUp<T>` | 普通 mock、spy，或受作用域保护的 static/construction mock |
+| `Deencapsulation.getField/setField` | 优先构造器或 setter；必要时使用项目已有的受控反射工具 |
+| `Deencapsulation.invoke` | 通过公共行为测试；不要默认直接测试私有方法 |
+
+## Stubbing
+
+普通 mock：
+
+```java
+when(repository.findById(id)).thenReturn(Optional.of(entity));
+```
+
+Spy 调用真实方法，使用 `when(spy.call())` 可能在设桩时就执行真实代码，因此优先：
+
+```java
+doReturn(value).when(spy).call();
+```
+
+Void 方法：
+
+```java
+doThrow(new IOException("failed")).when(client).close();
+```
+
+## 参数与验证
+
+若一次调用中使用 matcher，则该次调用的所有参数都应使用 matcher：
+
+```java
+verify(repository).save(eq(accountId), any(Order.class));
+```
+
+需要检查传入对象内容时使用 `ArgumentCaptor`，不要把复杂断言塞进自定义 matcher。
+
+## 静态方法
+
+仅在当前 Mockito 版本支持且遗留设计没有更小替代方案时使用。务必用 try-with-resources 限定作用域，避免污染其它测试：
+
+```java
+try (MockedStatic<ClockProvider> mocked = mockStatic(ClockProvider.class)) {
+    mocked.when(ClockProvider::now).thenReturn(fixedInstant);
+    assertEquals(expected, service.execute());
+}
+```
+
+不要并行共享同一个静态 mock。
+
+## 构造器拦截
+
+优先把对象创建移动到可注入的工厂或 supplier。无法在任务范围内调整遗留 seam 时，可用 `mockConstruction`，并检查构造次数或参数是否属于业务契约。
+
+## Final 类和方法
+
+现代 Mockito 通常可 mock final 类型，但是否可用取决于项目依赖与 mock maker 配置。先验证现有配置；不要同时添加相互冲突的 mock maker 文件。
+
+## 私有成员
+
+Mockito 不提供 `Deencapsulation` 的一比一替代。按以下顺序处理：
+
+1. 通过公共方法断言可观察结果。
+2. 将复杂私有逻辑提取到具备清晰职责、可直接测试的协作者，仅当生产设计因此改善。
+3. 使用已有包级 API 或测试 fixture。
+4. 只有维护遗留代码且范围受控时才用反射，并记录原因。
+
+不要为了让测试方便而把私有成员普遍改为 public。
+
+## JUnit 生命周期
+
+JUnit 5：
+
+```java
+@ExtendWith(MockitoExtension.class)
+class ServiceTest {
+    @Mock Repository repository;
+    @InjectMocks Service service;
+}
+```
+
+JUnit 4：
+
+```java
+@RunWith(MockitoJUnitRunner.class)
+public class ServiceTest {
+    @Mock Repository repository;
+    @InjectMocks Service service;
+}
+```
+
+若现有 JUnit 4 测试已有不可替换 runner，可使用 `MockitoRule` 或显式初始化，不要叠加两个 runner。
+
+## 依赖和构建清理
+
+迁移结束前搜索：
+
+- `mockit.` imports
+- `jmockit` Maven/Gradle dependency
+- Surefire、Failsafe、Gradle test task 或 IDE 配置里的 `-javaagent`
+- JMockit 专用启动参数与覆盖率组合参数
+- 被禁用、被排除或改名后无法被测试框架发现的测试
+
+Maven 多模块项目从拥有该测试的模块开始，再运行受影响聚合范围。Gradle 项目确认正确的 `test` source set 和过滤参数。每次都核对执行数量，避免把 `No tests found`、全量跳过或错误的模块当作通过。

package/templates/README.md

@@ -0,0 +1,3 @@
+# 模板
+
+可复用的文档、配置或项目骨架按类型建立子目录。模板中不要包含账号凭证、公司密钥或真实业务数据。