awesome-commit-planlisted

Turns a codebase into a commit plan: a navigation map of its modules and their dependency direction, then a split where every commit builds and tests on its own, so the series is bisectable end to end. Each commit is verified by replaying the ladder in a scratch clone against the repository's own gates, never asserted. Messages follow a strict ruleset that keeps machine-written prose out of the log. The only output is a plan file numbered #1 to #N, no dates, no preamble. Use when asked to 'split this project into commits', 'plan the commit history for this repo', 'how should I break this into commits', 'prepare a bisectable commit series', or in Russian 'разбей проект на коммиты', 'составь план коммитов', 'как разбить это на коммиты'. Takes a repository URL or a local path: '/awesome-commit-plan <url-or-path>'. Do not use to execute the plan against git history — that is awesome-git-history-rebuild; not to squash an existing history — awesome-git-history-reset; not to review a diff — awesome-code-review.
khasky/awesome-agent-skills · ★ 8 · Code & Development · score 78

Install: claude install-skill khasky/awesome-agent-skills

# Commit Plan Read a codebase, map how its parts depend on each other, and split it into a commit series where **every commit builds and its tests pass**. The output is one file: the commits, numbered `#1` to `#N`, each with its message and its exact file set. Nothing is committed, nothing is pushed, and the repository under analysis is never written to. **Why the plan is a separate artifact:** a split is a claim about a codebase — that these files form a unit, that this module compiles without the one landing three commits later, that this test has a subject to test. Claims are cheap to write and expensive to discover wrong at commit 14 of 40. A plan file is reviewable before any of that, re-splittable on one word from the user, and executable later by hand or by `awesome-git-history-rebuild`. ## Core principle **BISECTABLE IS A MEASURED PROPERTY, NOT A DESIGN GOAL.** A plan that says every commit builds has claimed something; a plan whose ladder was replayed in a scratch clone with the repository's own build and test commands run at every step has proven it. Phase 5 does the replay. A commit that fails its gate is regrouped and the ladder re-run — never shipped with a note that it "should" work. Four invariants hold throughout: - **Read-only against the user's code.** All work happens in a scratch clone or a temporary worktree. The user's checkout is never staged, committed, cleaned or checked out. If the run dies halfway, nothing of theirs moved. - **Every tracked pa