openrewrite-violations

OpenRewrite Violations

Create a branch named openrewrite-violations, then apply every configured OpenRewrite recipe that has violations one at a time, committing each recipe's changes as a separate commit with the message Fix violations of OpenRewrite rule: <recipe>.

If $ARGUMENTS is provided, use it as the branch name instead of openrewrite-violations.

Require a clean working tree

Run git status --porcelain. If there are uncommitted changes, stop and tell the user — this command creates commits and must start clean. Do not stash or discard their work.

Create the branch

Fetch the upstream default branch and create the new branch from it, so the commits land on top of current main:

git fetch origin
git switch -c openrewrite-violations origin/HEAD

Use a worktree (git worktree add) instead if the user is mid-work on another branch and you should not move their checkout.

Determine how this repo invokes OpenRewrite

Inspect the repo before running anything:

• If a mise.toml, .mise.toml, or .mise/ config exists, every Maven command must be prefixed with mise exec --, and the config must be trusted first: mise trust. Without the right JDK, the build fails with release version NN not supported.
• If a justfile defines rewrite-dry-run and rewrite <RECIPE> recipes (common in these repos), prefer them — they already activate the correct profile and recipe dependencies.
• Otherwise call the plugin directly: mvn rewrite:dryRun and mvn rewrite:run -Drewrite.activeRecipes=<recipe>. Check pom.xml for the rewrite-maven-plugin: if its configuration sits inside a <profile>, add --activate-profiles <that-profile> to every invocation.

Enumerate the recipes that have violations

Run the dry run and capture the full log (it takes minutes):

mise exec -- just rewrite-dry-run 2>&1 | tee .llm/rewrite-dryrun.log | tail -20

The dry run "fails" with Applying recipes would make changes when violations exist — that is the signal to proceed, not an error.