What problem does it solve? Large Maven multi-module builds are slow: -am pulls in too many modules, and compile/package phases trigger expensive goals like sources jars, shade, repackage, and javadoc. This Skill plans the shortest sufficient Maven lifecycle for Java changes and lets Check-All reuse prior build evidence instead of rebuilding. ## Core Features & Use Cases - Tiered Verification Modes: quick mode gives fast local feedback with optional source-stale compilation, final mode produces conservative, reusable evidence, and reuse mode lets Check-All validate evidence read-only without running Maven goals. - Reactor Trimming: Maps changed files to the minimal module set with -am for required upstreams, avoiding full-repo -amd builds and skipping expensive plugin bindings when not required. - Auditable Evidence Contract: Evidence binds Git HEAD, POM fingerprints, toolchain, argv, and logs, with states like reusable, partial, stale, failed, and blocked so downstream checks know exactly what is covered. - Use Case: After editing one module in a 50-module Java 8 monorepo, generate a quick compile plan scoped to that module and its upstreams, then let the final Check-All phase reuse the recorded evidence instead of triggering a full reactor build. ## Quick Start Ask the AI to use trellis-maven-verify to create a quick verification plan for the modules changed in the current Maven project.
