jade-core-build-fixer

Audit and repair Ant, Maven, or Gradle build files for Java 11+ migration.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/TheRealSeber/PolishedJADEite --skill jade-core-build-fixer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jade-core-build-fixer
Source: https://github.com/TheRealSeber/PolishedJADEite/tree/main/.claude/skills/jade-core-build-fixer
Command: npx skills add https://github.com/TheRealSeber/PolishedJADEite --skill jade-core-build-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes build-system blockers that prevent a JADE migration from starting, by checking whether the project can compile at the target Java version and applying the smallest safe build-only fixes.

Core Features & Use Cases

  • Build compatibility audit: Detects Ant, Maven, or Gradle build files and checks compiler settings against the target Java version.
  • Safe automated fixes: Updates only minimal, reversible build configuration such as source and target flags, then verifies the result.
  • Dependency risk detection: Flags Java 11+ compatibility problems like removed JAXB or CORBA dependencies before source migration begins.
  • Gate enforcement: Produces audit artifacts and stops the migration pipeline when the build cannot be made ready.
  • Use case: Use this Skill when a legacy Java project must be prepared for migration and the first requirement is proving that the build passes cleanly at the destination runtime.

Quick Start

Ask the skill to inspect the workspace build files, apply safe compatibility fixes, and verify that the build passes for the target Java version.

Frequently Asked Questions about jade-core-build-fixer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix Maven or Gradle build files for Java 11 migration compatibility?

To fix Maven or Gradle build files for Java 11 migration, you need a compatibility audit checking compiler settings against the target version. This Skill applies minimal reversible source and target flag updates, verifying the build passes before source migration begins.

What are common Java 11+ migration build blockers involving removed dependencies?

Java 11+ migration build blockers include removed dependencies like JAXB or CORBA. Dependency compatibility scanning flags these missing libraries before source migration begins, generating audit artifacts that halt the pipeline until resolved.

Can I automatically update compiler flags in Ant, Maven, and Gradle projects for target Java version compatibility?

You can automatically update compiler flags in Ant, Maven, and Gradle projects for target Java version compatibility. The process applies only minimal, reversible build configuration changes and then verifies the compilation result.

Does Java build migration fixing require Docker for execution and audit outputs?

Java build migration fixing requires Docker-based execution to isolate the environment and produce artifact-driven audit outputs. This containerized approach ensures idempotent minimal fixes are verified without altering local system configurations.

Why does my Java migration pipeline stop when the build cannot be made ready for the target runtime?

Java migration pipelines stop when the build cannot be made ready due to gate enforcement mechanisms. This feature produces audit artifacts and halts the process if target-version compilation fails or dependency compatibility issues remain unresolved.