Skip to content

2.3.0

Choose a tag to compare

@NintendaDev NintendaDev released this 01 Oct 06:29
· 286 commits to main since this release
eee78df

🚀 2.3.0 - Pull requests and resilient ultra planning

This release adds a built-in pull-request workflow and splits large plans into mergeable modules. Planning for very large features can now resume after an interruption, and verification reuses test results instead of rerunning them.

🧩 Resilient Ultra Planning

Ultra plans can now save their research to disk, so planning survives a context reset or a new session. /unikit-improve builds on that same research instead of re-exploring the codebase from scratch.

What's included
  • Choose standard (writes the plan directly, the default) or with saved state when starting an ultra plan; a standard plan over 12 phases is offered the switch
  • An interrupted saved-state plan resumes with /unikit-plan ultra <name> instead of starting over
  • /unikit-improve shows which research is still fresh and which code changed, and asks what to refine instead of re-exploring everything

✨ Pull Requests

A new /unikit-pr skill writes your PR description, opens or updates the branch's pull request, and merges it safely. Large plans now split into modules the base branch can merge one at a time.

What's included
  • /unikit-pr [remind|create|merge] - print the PR text, open/update it, or merge with a merge commit, capped by git.pull_requests.max_level
  • Enable checkpoints with git.pull_requests.checkpoints: true; every module but the last then stops for a PR before the next one starts
  • /unikit-verify Phases N-M checks one module - its tasks and its test state - before that module's PR
  • Merges only with a merge commit, only when the PR brings nothing new from the base branch, and only after you confirm
  • Adds GitHub's official remote MCP server (unchecked by default); your token is read from an environment variable and never written into a settings file

♻️ Smarter Test Runs

/unikit-verify now trusts the test run your plan already recorded instead of re-running everything. A phase's own test run can also be narrowed to just the changed modules instead of the whole suite.

What's included
  • New testing.run.use_affected_modules key narrows a phase checkpoint, and a /unikit-fix run, to the changed modules and whatever depends on them
  • testing.run.full_run_threshold_percent (default 30%) falls back to running everything once narrowing would not save much anyway
  • /unikit-verify --strict asks to run the full suite only when the recorded run no longer matches the code
  • A plan's closing full run is skipped and reused when nothing has changed since the last one

Full Changelog: 2.2.0...2.3.0