with one click
finish
// Use when implementation is complete — guides branch completion with commit, PR creation, or merge
// Use when implementation is complete — guides branch completion with commit, PR creation, or merge
| name | finish |
| description | Use when implementation is complete — guides branch completion with commit, PR creation, or merge |
| type | workflow |
Verify → commit → choose integration method → execute → clean up.
If $ARGUMENTS contains a branch or feature description, use it as context.
Before any commit, push, or PR creation:
$ARGUMENTS if provided; otherwise infer from the current branch name (first integer after the last /) or ask the user.hexis status read <issue>STATE: DONE: proceed.Run hexis:verify. Do not proceed to Step 2 if it fails.
If uncommitted changes exist, commit them following hexis:commit-principles rules.
Ask the user how they want to integrate the completed work. Present these four options:
<base-branch>git checkout <base-branch>
git pull
git merge <feature-branch>
<test command>
git branch -d <feature-branch>
P2 gate: Show the exact push command and wait for explicit approval. Do not push without approval.
git push -u origin <feature-branch>
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
- <2–3 lines of changes>
## Test Plan
- [ ] <verification step>
EOF
)"
PR title and body follow hexis:commit-principles type rules.
Report branch location. No further action.
Confirm first:
Tell the user exactly what will be permanently deleted:
<name><list><path> (if applicable)Require an explicit destructive confirmation before proceeding, but do not require any exact phrase. Any unambiguous confirmation is acceptable.
After confirmation:
git checkout <base-branch>
git branch -D <feature-branch>
For Options 1, 2, and 4:
git worktree list | grep <branch>
git worktree remove <worktree-path>
Option 3: keep the worktree.
Never:
--force-push without an explicit request[HINT] Download the complete skill directory including SKILL.md and all related files