code-quality-suite_skill

Overview

This skill combines code review best practices with unit testing guidance to improve Java code quality across design, maintainability, and test coverage. It runs the two capabilities in sequence so you get a clear set of actionable code-level fixes followed by concrete unit-test additions and improvements. The output is structured so teams can track review findings and testing tasks separately.

How this skill works

When enabled, the skill first inspects code for design issues, readability, potential bugs, API contracts, and maintainability using the code-review checklist. It then analyzes logic paths and test surface to recommend unit tests for happy paths, edge cases, and exception handling, plus suggestions to raise coverage. Responses separate code-change recommendations from test-case recommendations for easy triage.

When to use it

• Before merging significant feature or refactor pull requests
• When preparing code for release to reduce regressions
• During sprint code quality gates to enforce standards
• When coverage goals are unmet or tests are flaky
• For onboarding PRs from new contributors to ensure maintainability

Best practices

• Run the code-review checklist first, then apply unit-testing recommendations in a follow-up commit
• Provide structured output: list ‘Review Findings’ and ‘Test Actions’ separately for tracking
• Prioritize fixes that eliminate correctness and security risks before stylistic changes
• Focus unit tests on public behavior and critical edge cases rather than implementation details
• Use small, focused test commits and include constructive commit messages referencing review items

Example use cases

• A feature PR changing business logic: get both design issues and missing path tests identified
• A refactor that touches core services: confirm API stability and add regression tests for boundary conditions
• A module with low coverage: receive prioritized test cases to hit untested branches and exceptions
• A pull request with many TODOs: obtain actionable code fixes and matching unit tests to validate changes
• CI quality gate: produce structured findings the CI can fail fast on until key fixes and tests are implemented