tcrlisted

# TCR Commit Skill **TCR = Test && Commit || Revert** The core loop is simple: run the tests. If they pass, commit immediately. If they fail, revert the change. This forces small, safe steps and makes every commit a known-good state. ## The TCR Loop ``` 1. Make a small change (test or production code) 2. Run the relevant tests 3. GREEN? → git add <specific-files> + git commit (Conventional Commit message) 4. RED? → git checkout -- <changed-files> (revert to last green state) ``` The discipline is in the **size of the step**. If reverting feels painful, the step was too big. ## Commit Format Use Conventional Commits with the repository's branch/ticket prefix when present: `BRANCH-ID <type>: brief description`. Do **not** hardcode `Co-Authored-By` trailers. If the maintainer explicitly requires a non-AI co-author trailer, derive the identity from the user's global Git configuration instead of inventing it: ```bash git config --global user.name git config --global user.email ``` Only add a trailer when both values are configured and the repository policy allows it: ```text Co-Authored-By: <git config --global user.name> <<git config --global user.email>> ``` Never add AI attribution trailers. Types by TCR context: | Context | Type | Example | |---------|------|---------| | New test (characterization or unit) | `test` | `COMPANY-1234 test: add characterization test for calculateTotal` | | Test passes after refactor step | `refactor` | `COMPANY-1234 refactor: extra