speckit-complete-branch

To safely complete a spec branch, this skill runs preflight validation and cherry-picks accepted work into the base branch while keeping the spec branch intact. It requires workflow-record and improvement-candidates evidence to gate the process and avoid losing work.

Cherry-pick preflight validation is a stage gating process that checks dirty state, upstream tracking, and retrospective gates before completing a branch. It classifies tracked changes versus temporary artifacts to report blockers and ensure a safe cherry-pick sequence into the base branch.

Yes, spec-kit branch completion requires both a post-commit self-check and rubric validation. These retrospective checks act as workflow gates that must be satisfied before the safe cherry-pick sequence is executed to merge accepted work into master.

The safe cherry-pick sequence avoids remote pushes to preserve local branch state and prevent premature upstream changes during spec branch completion. This controlled completion ensures the spec branch is kept intact locally while only the validated base-branch change is finalized.

The best way to classify dirty state and temporary artifacts is using operational reporting that distinguishes tracked changes from temporary noise. This preflight classification reports blockers and ignored files, ensuring only validated work is cherry-picked into the base branch.