organized-commitslisted

# Organized Commits Make Git history a debug timeline: one intent per commit, useful messages, and no stranded work. Run only on an explicit commit, push, ship, or consolidation request. ## Safety - Read repository instructions and inspect status, branch, upstream, recent history, staged/unstaged diffs, untracked files, worktrees, and stashes before staging. - Preserve user-owned and unrelated changes. Stop if secrets, credentials, unexplained generated files, or ambiguous overlapping intent appear. - Never change Git configuration, rewrite published history, force-push a protected branch, or delete branches, tags, stashes, or worktrees without explicit authorization. - Push only when requested. Existing approval remains valid when the user already asked for commit and push in the same task. - Use merge, not rebase, to consolidate shared work. Create backup refs before integration. ## Workflow 1. Classify every changed path by intent: feature, fix, refactor, reorganization, removal, docs, test, build, CI, performance, style, or chore. 2. Group changes so each commit is independently understandable and does not leave the repository knowingly broken. Split mixed files by hunk only when the boundary is real. 3. Present the commit sequence when approval has not already been given. Include subject, intent, files, rationale, verification, and whether push is authorized. 4. Stage explicit paths or hunks. Audit `git diff --cached` before every commit. 5. Use an imperative conven