From 5d7f4633e14d8e4a75ed3291c1425a52a6268fa5 Mon Sep 17 00:00:00 2001 From: Brandon Lucas Date: Wed, 18 Feb 2026 21:09:27 -0500 Subject: [PATCH] docs: add explicit commit instructions to CLAUDE.md Co-Authored-By: Claude Opus 4.6 --- CLAUDE.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 0196f0a..69c5edc 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -71,7 +71,16 @@ cd ../packages/markdown && ../../lang/target/release/lux test **Do NOT commit if any check fails.** Fix the issue first. ### Commit after every piece of work -**After completing each logical unit of work, commit immediately.** Do not let changes accumulate uncommitted across multiple features. Each commit should be a single logical change (one feature, one bugfix, etc.). Use `--no-gpg-sign` flag for all commits. +**After completing each logical unit of work, commit immediately.** This is NOT optional — every fix, feature, or change MUST be committed right away. Do not let changes accumulate uncommitted across multiple features. Each commit should be a single logical change (one feature, one bugfix, etc.). Use `--no-gpg-sign` flag for all commits. + +**Commit workflow:** +1. Make the change +2. Run `./scripts/validate.sh` (all 13 checks must pass) +3. `git add` the relevant files +4. `git commit --no-gpg-sign -m "type: description"` (use conventional commits: fix/feat/chore/docs) +5. Move on to the next task + +**Never skip committing.** If you fixed a bug, commit it. If you added a feature, commit it. If you updated docs, commit it. Do not batch unrelated changes into one commit. **IMPORTANT: Always verify Lux code you write:** - Run with interpreter: `./target/release/lux file.lux`