---
name: commit-one-test-per-commit
description: "When committing test changes here, each test change gets its own commit explaining why"
metadata: 
  node_type: memory
  type: feedback
  originSessionId: d19a4e9a-1c8c-48a2-9b90-e8bd9d3cac73
---

When committing with conventional-commits in this repo, put **each test change in its own commit** with an explanation of *why* the change was made (not just what).

**Why:** The user reviews test changes individually and wants the rationale captured per-change in git history.

**How to apply:** One commit per test file (or per distinct test change). The commit body should explain the motivation — what the inverse/round-trip proves, what bug it catches, or what flakiness/assumption the fix addresses. Non-test prerequisite fixes (port bugs, harness/infra) get their own separate commits, committed first. Use `--signoff` and the `Assisted-by:` footer. See [[work-on-master-directly]].