# Ki Git > Governs portable Knowledge Islands Git working and commit conventions: Conventional Commit messages, shared-working-tree touched-path tracking, selection between single-working-copy main, single-working-copy branch with PR, and worktrees with PRs, safe Git hygiene, and the stale-lock guard's semantics. Use when preparing or reviewing a commit, coordinating human or agent changes in one working tree, choosing a working and review approach, recovering a stale Git lock, or clarifying who owns hook payload versus runtime registration. Does not configure GitHub repository settings, install hooks, or write agent settings; use ki-repo for repository configuration and ki-repo-dotfiles-chezmoi for runtime bindings. - Skill: `knowledgeislands/ki-git` (Agent Skill, multi-file: 14 files) - Install (CLI): `npx skillmds@latest add knowledgeislands/ki-git` - Raw SKILL.md: https://api.skillmd.com/api/skills/knowledgeislands/ki-git/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: knowledgeislands (https://skillmd.com/u/knowledgeislands) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/knowledgeislands/ki-git --- # Knowledge Islands Git conventions `ki-git` is the portable policy owner for Git and commit practice across Knowledge Islands repositories. It names three working approaches so branch choice and working-copy topology are explicit: `single-working-copy-on-main`, `single-working-copy-on-branch-with-pr`, and `worktrees-with-pr`. 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](references/standards-git.md) before preparing a commit, choosing a branch boundary, or assessing a stale lock. The hosted native rubric records the portable review prompts below. Its four policy 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. It deliberately has no mechanical policy checks or private Git executor yet. It does not install a hook, write runtime settings, or add a compatibility execution path. ## Boundaries - `ki-repo` owns repository configuration and GitHub settings, including branch-protection choices. - The harness owns `hooks/` payload layout; `ki-git` owns the stale-lock guard's portable safety semantics. - `ki-repo-dotfiles-chezmoi` owns 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 ` to render the portable review prompts. Treat the result as an unassessed judgment checklist until a reviewer records outcomes against the focused read-only evidence; it is not a pass/fail audit of Git state. 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-agentic-harness`. Invoked from an installed copy, stop and name the harness as the place to run it. Read [the source list](references/sources.md), 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.