원클릭으로
finishing-branch
Use when implementation is complete and a feature branch is ready to wrap up and merge
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when implementation is complete and a feature branch is ready to wrap up and merge
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when changing cogitation project settings (test/build/lint commands, branching conventions, graphify/codex toggles), or the user says "change config", "update settings", or "set test command"
Use when setting up a project for cogitation for the first time, or the user says "set up cogitation", "init", or "configure this project"
Use at the start of any conversation — establishes the cogitation workflow and requires invoking the right skill before responding, including before clarifying questions
Use for MEDIUM-sized work — new but contained behavior (one component, no architecture/data/API change) that deserves rigor without the design-doc + plan-doc ceremony of brainstorming
Use when the user wants to tailor the cogitation workflow — says "customise", "recustomise", "change the workflow", "make TDD less strict", "turn off finishing-branch", or wants a skill looser or disabled
Use when EC memories need cleanup — deduping, pruning stale entries, hygiene — or the user says "audit memories", "clean up EC", or "review what's stored"
| name | finishing-branch |
| description | Use when implementation is complete and a feature branch is ready to wrap up and merge |
Complete development work with verification, memory storage, and merge options.
Announce: "I'm using the finishing-branch skill to complete this work."
Verify Tests → EC Review → Present Options → Execute
Load project config:
ec_search:
query: project config
type: config
Run all verifications:
{test_command}
{lint_command}
{build_command}
If failures: Stop. Fix using @debugging before proceeding.
If passing: Continue.
Before finishing, review what's worth remembering.
Look at what changed:
git log --oneline main..HEAD
git diff --stat main..HEAD
Use AskUserQuestion:
{
"questions": [{
"question": "Any decisions, learnings, or patterns worth storing in EC?",
"header": "Memory",
"options": [
{ "label": "Yes", "description": "I'll describe what to store" },
{ "label": "No", "description": "Nothing notable this time" },
{ "label": "Let me suggest", "description": "Claude proposes, I approve" }
],
"multiSelect": false
}]
}
If "Let me suggest" - analyze the changes and propose:
For each approved memory:
ec_add:
type: decision|learning|pattern
area: [component]
content: [What to remember]
rationale: [Why it matters]
Load branch convention:
ec_search:
query: project config branch
type: config
{
"questions": [{
"question": "How do you want to finish this branch?",
"header": "Finish",
"options": [
{ "label": "Create PR", "description": "Push and open pull request" },
{ "label": "Merge locally", "description": "Merge to main locally" },
{ "label": "Keep as-is", "description": "I'll handle it later" },
{ "label": "Discard", "description": "Delete this branch and work" }
],
"multiSelect": false
}]
}
git push -u origin $(git branch --show-current)
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
- [What changed]
## Test Plan
- [ ] [Verification steps]
## EC Context
- [Relevant decisions/patterns consulted or created]
---
Design: docs/designs/YYYY-MM-DD-<topic>.md
Plan: docs/plans/YYYY-MM-DD-<topic>.md
EOF
)"
git checkout main
git pull
git merge <feature-branch>
{test_command} # Verify on merged result
git branch -d <feature-branch>
"Branch preserved. You can return to it later."
Confirm first:
"This will delete branch
<name>and all commits. Type 'discard' to confirm."
git checkout main
git branch -D <feature-branch>
After successful merge/PR:
"Branch complete. What's next?"
Suggest based on context: