Knowledge Islands Git conventions
Ordinary interactive work uses the repository's primary checkout by default. An unattended coordinator or another explicit isolation requirement may instead select a linked worktree under a safe runtime-owned root. Committing, pushing, and integrating into the primary branch remain separate authority decisions, except that a background run may fast-forward its own worktree branch into the local primary checkout's main once its gates pass, under the standard's worktree-run self-integration.
ki-git is the portable policy owner for Git and commit practice across Knowledge Islands repositories.
It names four working approaches so branch choice and working-copy topology are explicit: single-working-copy-on-main, single-working-copy-on-branch-with-pr, worktrees-with-pr, and worktrees-with-local-integration. A single working copy may be shared by human and agent threads: each thread tracks the files it may have changed, commits only its uncontested touched paths, and serialises the short Git write window that stages and advances shared HEAD.
Read the Git standard before preparing a commit, choosing a branch boundary, or assessing a stale lock.
The hosted native rubric records the portable review prompts below. Its COMMIT, BRANCH, HYGIENE and LOCK families are judgment-only: an AUDIT renders them as unassessed review work, not as a clean Git result. Before recording a judgment, gather the named read-only evidence (for example git status --short, git branch --show-current, and the proposed commit diff/message) and retain its outcome with the review. The CLEAN family is mechanical: CLEAN-2 to CLEAN-7 apply fixed rules to the read-only facts the ki host composes from mgit overview --json, and report each finding as a warning beside the owner's disposition judgment. Without those facts each criterion is unassessed, never passed. CLEAN-1 stays judgment-only while its only evidence is the provider's network pull-request list. The skill runs no Git command or private Git executor itself, and deleting a remote branch or closing a pull request always needs the owner's approval.
Every repository with a commit gate mechanically binds this skill's message vocabulary through a committed .githooks/commit-msg: the ki-engineering Commitlint contract where a package exists, and ki git check-message "$1" where none does. This skill does not install hooks, write runtime settings, or own the package toolchain; its native rubric retains the judgment that a proposed message accurately describes one completed unit.
Boundaries
ki-repoowns repository configuration and GitHub settings, including branch-protection choices.ki-repoowns the committed hooks' existence, binding and frame;ki-engineeringowns the Commitlint content for package-backed repositories;ki-gitowns the message policy that binding enforces.- The harness owns the runtime
hooks/payload layout;ki-gitowns the stale-lock guard's portable safety semantics. ki-repo-dotfiles-chezmoiowns runtime-specific Claude Code settings registration after it has selected a compatible payload.
Operating modes
Mode AUDIT
Read the selected repository's commit history and working-state evidence against the Git standard.
Run ki repo audit --skill ki-git --repo <repo> to render the portable review prompts and the CLEAN checks. Treat the judgment families as an unassessed checklist until a reviewer records outcomes against the focused read-only evidence; only the CLEAN checks assess Git state, and only when the host supplies mgit overview facts. It does not infer a missing configuration table or run a private wrapper.
Mode CONFORM
Apply the standard through reviewable Git actions: choose an appropriate commit boundary, use the documented message shape, and leave uncertain or unsafe lock state untouched.
Do not add a compatibility checker or automate commit-message rewriting.
Mode EDUCATE
Explain the portable Git boundary and route repository configuration to ki-repo, hook payload layout to the harness, and runtime binding to ki-repo-dotfiles-chezmoi.
EDUCATE creates no repository or user-state artifact.
Mode HELP
Explain the policy boundary, the available guidance modes, and the off-ramps above without inspecting or changing state.
Mode REFRESH
Precondition: REFRESH writes only to this skill's canonical files in ki-agent-backpack. Invoked from an installed copy, stop and name the harness as the place to run it.
Read the source list, re-check the Git and Conventional Commits sources and current Knowledge Islands practice, then propose any change to this skill and its standard.
Record the review date and findings in the source list; record implementation history in Git rather than a changelog.