harnesslisted

# Harness — pre-commit doc sync Lightweight check that runs right before commit. The goal is keeping four agent-facing docs aligned with reality. Self-triggered on non-trivial commits; the user can also invoke explicitly. ## When to use Run when **either** is true: - About to call `git commit` and the staged diff touches source code, config, or user-visible behavior. - The user asks: "harness" / "doc check" / "check before commit" / "sync docs" / equivalent. Skip when: - The diff is typo-only, comment-only, formatting-only, or pure test plumbing. - The diff only touches `.claude/`, `memory/`, or other agent-harness files. - This skill already ran on the same staged set earlier in the session. When the diff sits in the gray zone, ask the user one line ("harness check before commit? yes / skip") and default to skip if the change is small and self-contained. ## What to check Read `git status` + `git diff` (staged and unstaged). Then walk the table once: | File | Update when … | Skip when … | |---|---|---| | `CHANGELOG.md` | User-visible change (feature, bug fix, behavior change). Add one bullet to the unreleased section. | Internal refactor, tests, docs-only, typos. | | `conventions/architecture.md` | New module, migration, IPC channel, cross-cutting helper, or layering rule. | No structural change. | | `conventions/design-direction.md` | A UI pattern just hit its 3rd shipped instance. | Pattern is still 1–2 instances. | | `CLAUDE.md` | Change exposed a gotcha a fresh ag