auto-commitlisted

# Auto-Commit Generator Analyze pending git changes and group them into a structured commit plan written to `COMMITS.md` at the repo root. Default mode is plan-only — the user reads the file and either stages commits themselves or says the word for Claude to execute. On an explicit okay (see [Execution](#execution)), Claude runs the full branch → commits → push → PR chain against the plan, with no `Co-Authored-By:` trailer and without hardcoded side effects. ## Workflow 1. **Preflight — check for a prior plan.** Before scanning the diff, check whether `COMMITS.md` already exists at the repo root. If it does, parse its header comment (see [Header format](#header-format)) and compare `head-sha` + `tree-hash` to the current state: - **Exact match** → the existing plan is still current. Tell the user in one sentence (`COMMITS.md is current (HEAD @ <sha>, working tree unchanged) — delete or edit it if you want a regenerate.`) and stop. Do not overwrite. - **HEAD matches, tree drifted** → partial staleness. Preserve any user-added `## Notes` section (see step 5), then regenerate. - **No header, or header unparseable** → treat as a hand-written file. Do not overwrite silently; tell the user it exists without a header and ask whether to regenerate or bail. - **File absent** → normal path, continue. 2. **Analyze.** Run these in parallel: - `git status` (to see what's changed and in what state) - `git diff` (unstaged changes) - `git diff --cached` (staged chang