jade-core-tooling-scout

Probe OpenRewrite, PMD, and Checkstyle to record structured migration findings.

1|Updated Apr 14, 2026

Search Tags:#migration #java #openrewrite #static-analysis #checkstyle #pmd #tooling-scout

Ready to run

npx skills add https://github.com/TheRealSeber/PolishedJADEite --skill jade-core-tooling-scout

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jade-core-tooling-scout
Source: https://github.com/TheRealSeber/PolishedJADEite/tree/main/.claude/skills/jade-core-tooling-scout
Command: npx skills add https://github.com/TheRealSeber/PolishedJADEite --skill jade-core-tooling-scout

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill discovers which parts of a legacy Java migration can be assisted by static analysis tools before anyone makes manual code changes, helping teams separate automatable work from human-only fixes.

Core Features & Use Cases

Tool probing: Detects whether OpenRewrite, PMD, and Checkstyle are available in the workspace or on the machine.
Dry-run discovery: Runs read-only scans to identify applicable rewrite recipes and migration-relevant violations without rewriting source code.
Evidence reporting: Writes structured JSON reports and raw findings that can be merged into the breaking-changes manifest with provenance.
Use case: Ideal for a JADE migration pipeline that needs to validate a modern JDK, scout tooling coverage, and prepare the next phase of automated or manual remediation.

Quick Start

Ask the skill to validate the modern JDK, probe the workspace for OpenRewrite, PMD, and Checkstyle, run read-only discovery, and merge any findings into the breaking-changes manifest.

Frequently Asked Questions about jade-core-tooling-scout

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

FAQPage Schema

How do I find auto-fixable Java migration work before making manual code changes?▼

To find auto-fixable Java migration work, you can run read-only static analysis discovery using OpenRewrite, PMD, and Checkstyle. This process probes your legacy workspace to identify applicable rewrite recipes and migration-relevant violations without modifying your source code.

How do I detect OpenRewrite, PMD, and Checkstyle availability for a legacy Java migration?▼

You can detect OpenRewrite, PMD, and Checkstyle availability by probing the workspace and local machine environment. Tool probing checks for these static analysis binaries to determine which automated migration coverage is possible before running scans.

Does Java migration discovery with OpenRewrite require a specific JDK version?▼

Java migration discovery with OpenRewrite requires a modern JDK to run the tooling binaries. The process performs read-only workspace analysis to validate the environment and ensure the necessary static analysis tools can execute properly.

Can I run OpenRewrite recipes in a dry-run mode to see migration violations without rewriting code?▼

You can run OpenRewrite recipes in dry-run discovery mode to identify applicable recipes and migration-relevant violations without rewriting source code. This read-only scan separates automatable migration work from human-only fixes safely.

What is the best way to report static analysis findings for a JADE migration pipeline?▼

The best way to report static analysis findings for a JADE migration pipeline is to generate structured JSON reports and raw findings. These artifacts capture provenance and can be merged directly into the breaking-changes manifest for validation and reporting.

Why does my static analysis tooling scout fail to probe the workspace?▼

Static analysis tooling scouting fails if a modern JDK is not installed or if OpenRewrite, PMD, and Checkstyle binaries are unavailable in the workspace. The process requires read-only access to validate the environment and execute tooling probes successfully.