菜单
Use PIT (Pitest) mutation testing to identify weak tests and improve test quality in Java projects. Finds tests that pass but don't actually verify behavior correctly. Use when improving test suite quality beyond line coverage metrics.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
RFC-39 compliant API best practices for Java services. Covers request/response patterns, error handling, pagination, versioning, and authentication standards. Use when designing or reviewing REST APIs in Java services.
RFC-29 compliant changelog management with Common Changelog format and Unreleased section extension. Validates changelog on commits, generates from git history, and ensures all merged PRs are documented. Use when setting up changelog workflows or retrofitting existing repositories.
Systematic workflow for CodeRabbit reviews - local CLI, PR threads, and commit attribution
Enforces consistent coding standards across the codebase including naming conventions, code organization, and documentation requirements. Use when writing new code, reviewing pull requests, or refactoring existing code.
Database integration patterns for Java services using jOOQ and Flyway. Covers code generation, read/write splitting, migration guidelines, and version compatibility. Use when setting up or maintaining PostgreSQL integration.
Version catalog strategy, dependency management, BOMs, and version constraints for Java/Gradle projects. Covers version centralization, never-downgrade policy, bundle patterns, resolution strategies, and compatibility matrices.
| name | mutation-testing |
| description | Use PIT (Pitest) mutation testing to identify weak tests and improve test quality in Java projects. Finds tests that pass but don't actually verify behavior correctly. Use when improving test suite quality beyond line coverage metrics. |
| compatibility | Java projects using Gradle 8.x+ with JUnit 5 or Spock |
| metadata | {"version":"2.0.0","technology":"java","category":"testing","tags":["java","gradle","testing","mutation-testing","pitest","quality"]} |
Use PIT mutation testing to identify tests that pass but don't verify behavior correctly.
📚 references/ - Detailed documentation
bash java/scripts/check-pitest-readiness.sh
Copy java/templates/pitest.gradle to gradle/pitest.gradle and apply in build.gradle.
# QUICK level - fast feedback
./gradlew pitest -Ppitest.mutators=DEFAULTS
# STANDARD level - recommended
./gradlew pitest -Ppitest.mutators=STRONGER
# COMPREHENSIVE level - thorough
./gradlew pitest -Ppitest.mutators=ALL
open build/reports/pitest/index.html
Focus on SURVIVED mutants - these indicate weak tests.
Add specific assertions that kill the surviving mutants.
High line coverage with low mutation score = tests run code but don't verify results.
| Level | Mutators | Use Case | Time |
|---|---|---|---|
| QUICK | DEFAULTS (~11) | Initial analysis, CI | 1x |
| STANDARD | STRONGER (~14) | Regular improvement | 1.5x |
| COMPREHENSIVE | ALL (~30+) | Critical logic | 3-5x |
| Status | Meaning | Action |
|---|---|---|
| Killed | Test detected mutation | Good |
| Survived | Test missed mutation | Improve test |
| No Coverage | No test covers code | Write test |
| Timed Out | Infinite loop | Usually OK |
| Reference | Description |
|---|---|
| references/intensity-levels.md | Detailed mutator descriptions |
| references/improving-tests.md | Patterns for killing mutants |
| references/configuration.md | PIT configuration options |
| references/troubleshooting.md | Common issues and solutions |
| Skill | Purpose |
|---|---|
| java-testing | Test configuration |
| java-coverage | JaCoCo coverage |