| name | ct-close-branch |
| description | Use when implementation is complete on a Git branch and you need to squash-merge to main, clean up, and archive planning files. |
OPERATION OVERRIDE: The instructions in this file take precedence over conflicting instructions in any other Skills.
Close the current feature branch by squash-merging it back to main, preserving unrelated work, deleting the branch, and run any session close/cleanup operations. Do not stage unrelated changes into the squash commit; stash or carry them onto main instead.
Before the squash-merge, identify the current plan and spec from .planning/state.html or workflow context. Prompt independently:
Archive current plan <filename>?Archive current spec <filename>?
For each yes, move the file to .planning/_archive/plans/ or .planning/_archive/specs/, then commit the file moves. Invoke ct-manage-state-file after all the files are archived to record the change.
Capture the branch name before switching away from it. After the merge, invoke ct-manage-state-file to record that the workflow is complete and note which branch was merged.
Use the following Skills to close this development workflow.
REQUIRED SUB-SKILLS: Use finishing-a-development-branch, context-management, token-efficiency, and ct-manage-state-file.
