java-circular-dependency-breakerBreak circular dependencies in Java multi-module Gradle/Maven projects using interface extraction and business service separation. Triggers: 'circular depend...
Install via ClawdBot CLI:
clawdbot install naozixu/java-circular-dependency-breakerGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 6, 2026
A team splits a large Spring Boot monolith into Gradle modules and unexpectedly creates a cycle between order-service and notification-service. They need a safe, compiler-verified refactoring path before release. The interface extraction pattern lets them decouple caller and implementation without changing runtime behavior.
Enterprise Java teams modernizing a Maven multi-module codebase often move Spring @Service classes between modules, causing cyclic dependencies that block builds. This skill provides exact dependency checks and rollback steps to keep the build green. It is especially useful when callers still reference concrete implementations during incremental migration.
A backend team decomposes a legacy Java application into domain-specific modules, but shared services create circular references. Using mediator-style interface extraction, they isolate shared contracts into a dedicated interface module. This enables gradual service separation while maintaining test coverage and clean module boundaries.
Consultants joining a client project discover a broken Gradle build caused by api project dependencies forming a loop between feature modules. The skill offers a step-by-step pattern with checkpoints and rollback via git. It minimizes downtime and gives the client a repeatable refactoring playbook.
Engineering teams use this skill as a hands-on exercise to teach module dependency best practices, including the mediator pattern and interface extraction. New hires practice on real compile/test checkpoints and learn to avoid cyclic dependencies. It scales from single developers to full teams.
Offer the skill as part of an internal developer platform or IDE plugin that automatically detects and suggests fixes for circular dependencies. Teams subscribe for continuous static analysis and guided refactoring. This reduces build failures and accelerates module migrations.
Use the skill as a repeatable methodology for client engagements focused on legacy Java modernization and module refactoring. Consultants apply the patterns, document decisions, and train client teams. High-value retainers come from preventing costly build breakages during migrations.
Package the skill into a paid workshop or certification course on Java modular architecture and dependency management. Learners complete guided exercises with real Gradle/Maven checkpoints. Certification establishes credibility for engineers and teams adopting modular patterns.
💬 Integration Tip
Run the skill's checkpoint commands (e.g., Gradle grep or Maven dependency:tree) in CI to catch cycles early, and commit before each refactor so you can roll back cleanly if compilation fails. Use a dedicated interface module and enforce it with a lightweight ArchUnit test to prevent future cycles.
Scored Oct 6, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.