What problem does it solve?
After migrating Groovy tests to Java, subtle quality regressions (weakened assertions, wrong types, lost config) slip through. This Skill systematically checks migrated Java test files against a shared rule set so violations are caught before merge.
Core Features & Use Cases
- Rule-based detection: Runs grep-based checks for rules like RULE-C01, RULE-F01, and RULE-C05, plus LLM-based structural checks for rules without grep patterns.
- Structured findings: Emits FINDING blocks with file, line, rule, severity (BLOCKER/WARNING/STYLE), excerpt, and suggested fix, grouped by severity.
- Auto-fix workflow: Offers to automatically fix BLOCKERs and WARNINGs, runs spotlessApply per module, and re-verifies with grep.
- Use Case: After running a Groovy-to-Java test migration on a branch, invoke this Skill to audit all newly added src/test/java files and fix blocker-level issues before opening a pull request.
Quick Start
Review the Java test files migrated on my current branch against the quality rules and fix any blockers and warnings.