Initial implementation

Author: radoslaw-panuszewski

.editorconfig

@@ -0,0 +1,12 @@
+version: 2
+
+updates:
+  - package-ecosystem: "gradle"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/dependabot.yml

@@ -0,0 +1,89 @@
+name: CI
+
+on:
+  pull_request:
+  workflow_dispatch:
+  push:
+  release:
+    types: [ published ]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  unit-tests:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-java@v5
+        with:
+          java-version: 21
+          distribution: temurin
+
+      - uses: gradle/actions/setup-gradle@v5
+        with:
+          cache-read-only: false
+
+      - run: ./gradlew test
+
+      - name: Junit report
+        uses: mikepenz/action-junit-report@v4
+        if: success() || failure()
+        with:
+          report_paths: '**/test-results/*/*.xml'
+
+  publish-to-homebrew:
+    runs-on: ubuntu-latest
+#    if: github.event_name == 'release'
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-java@v5
+        with:
+          java-version: 21
+          distribution: temurin
+
+      - uses: gradle/actions/setup-gradle@v5
+        with:
+          cache-read-only: false
+
+#      - run: ./gradlew check
+
+      - id: publish
+        run: ./gradlew publish
+        env:
+          SONATYPE_USERNAME: ${{ secrets.SONATYPE_USERNAME }}
+          SONATYPE_PASSWORD: ${{ secrets.SONATYPE_PASSWORD }}
+          JRELEASER_GITHUB_TOKEN: dummy
+
+      - id: generate-token
+        uses: actions/create-github-app-token@v1
+        with:
+          app-id: ${{ secrets.ALLEGRO_HOMEBREW_APP_ID }}
+          private-key: ${{ secrets.ALLEGRO_HOMEBREW_PRIVATE_KEY }}
+          owner: allegro
+          repositories: homebrew-tap
+
+      - name: Checkout Homebrew repository
+        uses: actions/checkout@v4
+        with:
+          repository: allegro/homebrew-tap
+          path: homebrew-tap
+          token: ${{ steps.generate-token.outputs.token }}
+
+      - name: Replace file in Homebrew repository
+        run: |
+          ls -lah allwrite-runner/build/jreleaser/assemble/allwrite/jlink
+          cp allwrite-runner/build/jreleaser/package/allwrite/brew/Formula/allwrite.rb homebrew-tap/Formula/allwrite.rb
+          git add homebrew-tap/Formula/allwrite.rb
+
+      - name: Commit changes in Homebrew repository
+        uses: dsanders11/github-app-commit-action@v2
+        with:
+          owner: allegro
+          repo: homebrew-tap
+          message: 'Release allwrite ${{ steps.publish.outputs.published-version }}'
+          token: ${{ steps.generate-token.outputs.token }}
+          working-directory: ./homebrew-tap

.github/workflows/ci.yml

@@ -0,0 +1,13 @@
+.gradle
+.idea
+**/build
+**/.kotlin
+
+# OpenCode
+.classpath
+.project
+.factorypath
+.settings/
+bin/
+
+OPEN_SOURCE_PLAN.md

.gitignore

@@ -0,0 +1,4 @@
+# AGENTS.md
+
+You MUST always follow these rules:
+* Do not write any comments in the code

AGENTS.md

@@ -0,0 +1,79 @@
+# Contributing guide
+
+## How to write a recipe?
+
+All recipe implementations are kept in the `allwrite-recipes` module.
+
+In general, you should follow the official [Authoring Recipes](https://docs.openrewrite.org/authoring-recipes) docs from OpenRewrite.
+
+However, `allwrite` has some custom features that you can use.
+
+### Visibility
+
+Every recipe within `allwrite-recipes` must provide the `visibility:[internal/public]` tag. Public recipes will be presented to the user via
+`allwrite ls` command.
+
+### Friendly names
+
+Every public recipe must provide a friendly name in the form of 2 tags:
+* `group:<someGroup>`
+* `recipe:<someRecipe>`
+
+For example, the following set of tags [`group:workflows`, `recipe:introduceSetupGradle`] will result in a recipe that can be executed like that:
+```
+allwrite run workflows/introduceSetupGradle
+```
+
+### Convenient base classes
+
+For convenience, you can extend either `AllegroRecipe` or `AllegroScanningRecipe`. It will build all required tags for you:
+```kotlin
+class SomeRecipe : AllegroRecipe(
+    displayName = "Some recipe", // optional, defaults to class name
+    description = "Some description.", // optional, defaults to displayName + '.'
+    visibility = PUBLIC, // optional, defaults to INTERNAL
+    group = "some-group", // required if the visibility is PUBLIC
+    recipe = "some-recipe" // required if the visibility is PUBLIC
+) {
+    // your implementation
+}
+```
+
+### Limiting which files should be parsed
+
+> [!TIP]
+> It may be very useful for improving performance and overcoming OpenRewrite issues with parsing Groovy files
+
+If your recipe is only interested in very specific files (for example it only modifies the `tycho.yaml` file) you can implement the `ParsingAwareRecipe`
+interface:
+```kotlin
+class SomeRecipe : AllegroRecipe(), ParsingAwareRecipe {
+
+    override fun selectFilesToParse(inputFiles: List<Path>): List<Path> {
+        // return the files to be parsed
+    }
+}
+```
+
+## Architecture
+
+The `allwrite` is a modular project, utilizing dependency injection capabilities from the [Koin](https://github.com/InsertKoinIO/koin) framework.
+
+It consists of the following Gradle modules (that may contain one or more Koin modules):
+* `allwrite-runner` - provides both Application and Infrastructure layers for the CLI app
+* `allwrite-runtime` - provides core implementation interacting directly with the OpenRewrite runtime; equivalent of the Domain layer
+* `allwrite-recipes` - contains OpenRewrite recipes to be executed by `allwrite-runner`
+* `allwrite-completions` - provides annotation processors generating CLI auto-completions
+
+The below diagram shows Koin modules, not Gradle modules. The rule of thumb is: we don't extract Koin module as a separate Gradle module unless required
+by the build logic. For example, `allwrite-runtime` must be Gradle module, because it is used by both `allwrite-runner` (at app runtime)
+and `allwrite-completions` (at app compile time).
+
+Please keep the diagram up-to-date by editing `architecture.puml` file with the help of [PlantUML IntelliJ Plugin](https://plugins.jetbrains.com/plugin/7017-plantuml-integration) and replacing the rendered PNG.
+
+If you don't like installing IntelliJ plugins, edit `architecture.puml` and execute the following command:
+```bash
+docker run --rm -v $(pwd):/app -w /app ghcr.io/plantuml/plantuml plantuml docs/architecture.puml
+```
+
+![](docs/architecture.png)

CONTRIBUTING.md

@@ -0,0 +1,6 @@
+FROM eclipse-temurin:21
+RUN apt update
+RUN apt install -y git
+ADD ./allwrite-runner/build/distributions/allwrite.tar /app
+RUN ln -s /app/allwrite/bin/allwrite-runner /allwrite
+ENTRYPOINT []

Dockerfile

@@ -0,0 +1,13 @@
+Copyright 2026 Allegro.pl
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

LICENSE

@@ -1,2 +1,35 @@
 allwrite
 ========
+
+A CLI tool and a collection of [OpenRewrite](https://docs.openrewrite.org/) recipes for automated code transformations across YAML, Gradle, Java/Kotlin, and Spring projects.
+
+It wraps OpenRewrite's runtime into a user-friendly CLI that can run recipes by name, integrate with GitHub Actions, and work with Dependabot PRs.
+
+## Usage
+
+Installation:
+
+```bash
+brew install allwrite
+```
+
+Run a recipe by friendly name:
+
+```bash
+allwrite run springBoot/upgrade 3 4
+```
+
+Run a recipe by fully-qualified name:
+
+```bash
+allwrite run --recipe pl.allegro.tech.allwrite.recipes.SpringBoot4
+```
+
+## Recipes
+
+The `allwrite` CLI comes with all the free OpenRewrite migrations bundled (Java/Kotlin refactoring, Spring Boot upgrades, etc.).
+
+In addition, it provides a collection of custom recipes that aim to fill the gaps. See [RECIPES.md](RECIPES.md) for the full list.
+
+If you're a library maintainer and want to automate the migration process for your users (or just have prepared a recipe that may be useful for others),
+we would love to see your contribution! ❤️