Add middleware-kit CLI for creating and updating projects - #22
Merged
Conversation
johnnygreco
marked this pull request as ready for review
July 23, 2026 19:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
middleware-kitpackage and itsmkitcommand.mkit createfor new Python and Rust middleware projects.mkit updateto change a project to the latest OpenShell release or a release you choose.mkit updaterefreshes the proto, generated Python files or Rust build files, lockfile, and manifest. It leaves implementation files alone.middleware-kitas the generator.Tests
uv run ruff format --check .uv run ruff check .uv run ty checkuv run pytest— 85 tests, 95.50% coverageuv buildmkitcommand.mkit, created and tested Python and Rust projects, and updated a Python project. The update kept user files and caches intact and wrote the expected manifest and proto checksum.Review
Correctness, security, maintainability, documentation, and UX reviewers checked the change. The UX reviewer ran the full create and update flows in an isolated environment. All reported issues were fixed, and the reviewers found no remaining problems.