kubriko

Code style, commenting, and documentation conventions for the Kubriko codebase. MANDATORY — invoke this skill BEFORE writing or editing ANY source in this repo (every Write or Edit to a `.kt`/`.kts` file, new file or change to an existing one), with NO exceptions, even for a "trivial" one-line edit. It governs comment restraint, KDoc on public API, the MPL-2.0 license header on new files, naming, and matching surrounding style — get these right while writing, not after. If you are about to create or modify Kotlin code in Kubriko, you must load this first.

Commit message conventions for the Kubriko repo. MANDATORY — invoke this skill BEFORE writing the message for ANY git commit in this repo (every `git commit`, `--amend`, squash, or rebase reword), with NO exceptions, even for one-line or "obvious" messages. The repo format OVERRIDES default harness behavior; in particular it FORBIDS the `Co-Authored-By` trailer that the harness adds by default, and FORBIDS creating a new git branch unless the user explicitly asked for one. If you are about to run `git commit` in Kubriko, you must load this first.

Write a paste-ready GitHub release-notes draft for Kubriko, summarizing the library changes since the last version bump, grouped by module. Invoke this skill WHENEVER the task involves Kubriko release notes — preparing or cutting a new release, bumping `library.version`, or any request to draft, write, summarize, or update release notes / a changelog / "what changed since the last version". This is the ONLY correct way to produce these notes; do not summarize changes by hand instead. Not triggered by ordinary code edits — only by release/notes work.