commit-history-reviewlisted

# Commit History Review ## Core Question Is this branch history coherent and reviewable, and what history cleanup would improve it if the user chooses to rewrite? ## When To Use Use this skill when: - the user asks whether commit history is clean - the branch has WIP, fixup, squash, revert, or duplicate commits - the user wants a review-only recommendation before PR - the user wants to know whether commits should be split, squashed, or reworded ## When Not To Use Do not use this skill when: - performing rebase, squash, amend, or force-push - creating commits - changing staged content - merge readiness as a whole Route to: - actual rewrite or commit regrouping routes to `atomic-commits` or `undo-recover` depending risk - PR narrative routes to `pr-review-prep` - range diagnosis routes to `repo-state-diagnosis` ## Required Evidence Before action, inspect or establish: - branch range or merge-base - commit subjects and bodies - changed files per commit - fixup/squash/WIP/revert markers - public/shared branch status when available - project commit convention evidence No-evidence rule: - Do not make strong claims without observed evidence. - State assumptions when proceeding under incomplete evidence. - Stop when missing evidence affects safety, correctness, user work, remote state, or irreversible action. ## Operating Contract You MAY: - inspect relevant repository state and project files. - generate a plan, report, or local artifact within the declared risk sco