speckit-checkpoint-commit

Checkpoint commits prevent hard-to-review, mixed-purpose changes by capturing the repository state at meaningful spec-kit workflow phases. This ensures each phase of work is committed cleanly and can be inspected or rolled back independently.

After completing a spec-kit planning phase, stage all current repository changes and provide a single descriptive commit message reflecting the completed work. This ensures pre-implementation phases like specify, clarify, plan, and analyze are captured cleanly.

Yes, git staging of all current changes is required before creating a checkpoint commit. The automation then applies a single descriptive commit message reflecting the completed spec-kit phase or implementation milestone.

Create checkpoint commits during implementation after completing a task, a logical task group, or a self-contained unit of work. This ensures repository changes at logical implementation milestones are captured for better traceability by reviewers.

Using checkpoint commits prevents hard-to-review, mixed-purpose changes by capturing the repository state at meaningful workflow intervals. This allows each phase of work to be inspected or rolled back independently by reviewers.