← ClaudeAtlas

ki-gitlisted

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.
knowledgeislands/ki-agentic-harness · ★ 0 · Code & Development · score 76
Install: claude install-skill knowledgeislands/ki-agentic-harness
# 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.