commitlisted

# Commit & Self-Maintain CLAUDE.md + Memory ## Step 1: Commit 1. Run `git status` (never use `-uall`), `git diff --cached`, and `git log --oneline -5` in parallel. 2. Analyze all staged changes. Draft a concise commit message: - Use conventional commits: `feat:`, `fix:`, `refactor:`, `docs:`, `chore:`, etc. - Focus on **why**, not what. - NEVER include `Co-Authored-By` lines or mention Claude. 3. Stage relevant untracked files if needed (prefer specific files over `git add .`). 4. Commit using a HEREDOC for the message. Do NOT use `--no-verify`. 5. Run `git status` to confirm success. ## Step 2: Update ROADMAP.md After committing, update `ROADMAP.md` at the project root. 1. **Gitignore rule:** `ROADMAP.md` should normally be tracked by git and committed alongside the changes it describes. Only leave it gitignored if that specific repo already does so. 2. Read the current `ROADMAP.md` (create it if it doesn't exist). 3. **Prepend** a new entry at the top (most recent first) with this format: ``` ## [commit hash short] - [commit message] ([date YYYY-MM-DD]) **Problem:** [What was wrong or missing - 1-2 sentences] **Solution:** [What was done to fix/implement it - 1-2 sentences] **Files changed:** [list of key files touched, not exhaustive] --- ``` 4. Keep entries concise and useful. Focus on the **why** and the **how**, not line-by-line diffs. 5. If the commit is trivial (typo fix, formatting), still add an entry but keep it minimal. ## Step 3: Evaluate CLA