Skip to content

2.2.0

Choose a tag to compare

@NintendaDev NintendaDev released this 26 Sep 07:29
· 327 commits to main since this release
c46a15a

🚀 2.2.0 - Rule topics, readable commits and a plan archive

Project rules can now be split into topics that load only when relevant. Commits read like notes for the team, and finished plans move to an archive.

✨ Project Rule Topics

.unikit/RULES.md can now keep common rules at the top and move the rest into topic files in .unikit/rules/. Each topic loads only when the work at hand matches it; existing flat files keep working and are offered the split.

What's included
  • New rules go into the matching topic, a new topic, or ## Common when the right place is unclear
  • /unikit-rules optimise previews the move, and a bundled script refuses to write if any rule would be lost or changed
  • /unikit-rules prune proposes deletions with evidence and removes only what you choose; contradicting rules are resolved, not deleted
  • Planning, implementation, verification and background checks load the topics that match their work
  • Every /unikit-rules mode says what it is about to do before it reads anything

✨ Readable Commits and a Plan Archive

/unikit-commit now writes what changed and why it matters, then at most three lines of technical detail. The new /unikit-archive moves finished plans out of the active list.

What's included
  • Commits link their plan with a Plan: <folder> trailer instead of phase and task numbers
  • At an /unikit-implement checkpoint, Yes, and from now on commit without asking commits the rest of the session without questions or pushes; safety errors still stop it
  • Every commit the pipeline makes, including during coordinated runs, goes through /unikit-commit
  • /unikit-archive lists plans with their created and last-change dates; an unfinished plan moves only when you pick it and is marked as unfinished
  • The archive never deletes or commits anything, and /unikit-plan and /unikit-explore still read archived plans as history

♻️ Test Runs for a Phase Range

When one /unikit-implement call covers several test points, it lists them and asks once: run the tests a single time at the end, or at every point. Words in the call, such as Phases 5-6, tests at the end of phase 6, answer in advance.

Details
  • The answer holds for that call only, so the next call can choose differently
  • A merged point's extra checks, such as a negative control or a manual smoke test, run at the point that is kept
  • Test runs left over from an earlier call are recorded and closed by the run that carries them
  • The implement coordinator asks the same question before its first layer

✨ Research That Keeps Your Words

/unikit-explore now logs the conversation word for word as it happens and ties each requirement to what you said. Before saving, it asks you to confirm requirements it inferred, changed or found ambiguous.

What's included
  • Each requirement is marked as stated by you, inferred, or different from your proposal
  • One confirmation question per requirement; agents without a question tool print numbered options
  • Requirements you never confirmed become open questions instead of reaching the plan
  • A session that ends before saving leaves an unfinished research you can resume with /unikit-explore <folder>

🐛 Fixes

  • The configured language now holds for the whole session, including results passed back from background agents
  • Split commits no longer pick up edits you left unstaged
  • A direct editor edit no longer goes ahead when the safety commit before it is cancelled; the task returns to manual
  • /unikit-implement uses the branch's own plan while it has pending work, instead of asking which plan to run
  • /unikit-rules compact stops with a note when the file holds no rules

🛠 Internal Improvements

Technical changes
  • Long skill instructions moved into reference files that are read only when a run needs them
  • The research-link rules live in one installed file, .unikit/system/research-link.md, instead of four copies
  • The test suite caps every SKILL.md at 70 000 bytes
  • New maintainer pages under docs/skills/ explain why the skill rules are written as they are

Full Changelog: 2.1.0...2.2.0