개발 브랜치 마무리
개발 브랜치를 닫고, 변경 사항을 병합하며, 작업 공간을 정리합니다.
SKILL.md Definition
Finishing a Development Branch
Overview
Guide completion of development work by presenting clear options and handling chosen workflow.
Core principle: Verify tests → Present options → Execute choice → Clean up.
Announce at start: "I'm using the finishing-a-development-branch skill to complete this work."
The Process
Step 1: Verify Tests
Before presenting options, verify tests pass:
# Run project's test suite
npm test / cargo test / pytest / go test ./...
If tests fail:
Tests failing (<N> failures). Must fix before completing:
[Show failures]
Cannot proceed with merge/PR until tests pass.
Stop. Don't proceed to Step 2.
If tests pass: Continue to Step 2.
Step 2: Determine Base Branch
# Try common base branches
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
Or ask: "This branch split from main - is that correct?"
Step 3: Present Options
Present exactly these 4 options:
Implementation complete. What would you like to do?
1. Merge back to <base-branch> locally
2. Push and create a Pull Request
3. Keep the branch as-is (I'll handle it later)
4. Discard this work
Which option?
Don't add explanation - keep options concise.
Step 4: Execute Choice
Option 1: Merge Locally
# Switch to base branch
git checkout <base-branch>
# Pull latest
git pull
# Merge feature branch
git merge <feature-branch>
# Verify tests on merged result
<test command>
# If tests pass
git branch -d <feature-branch>
Then: Cleanup worktree (Step 5)
Option 2: Push and Create PR
# Push branch
git push -u origin <feature-branch>
# Create PR
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
<2-3 bullets of what changed>
## Test Plan
- [ ] <verification steps>
EOF
)"
Then: Cleanup worktree (Step 5)
Option 3: Keep As-Is
Report: "Keeping branch
Don't cleanup worktree.
Option 4: Discard
Confirm first:
This will permanently delete:
- Branch <name>
- All commits: <commit-list>
- Worktree at <path>
Type 'discard' to confirm.
Wait for exact confirmation.
If confirmed:
git checkout <base-branch>
git branch -D <feature-branch>
Then: Cleanup worktree (Step 5)
Step 5: Cleanup Worktree
For Options 1, 2, 4:
Check if in worktree:
git worktree list | grep $(git branch --show-current)
If yes:
git worktree remove <worktree-path>
For Option 3: Keep worktree.
Quick Reference
| Option | Merge | Push | Keep Worktree | Cleanup Branch |
|---|---|---|---|---|
| 1. Merge locally | ✓ | - | - | ✓ |
| 2. Create PR | - | ✓ | ✓ | - |
| 3. Keep as-is | - | - | ✓ | - |
| 4. Discard | - | - | - | ✓ (force) |
Common Mistakes
Skipping test verification
- Problem: Merge broken code, create failing PR
- Fix: Always verify tests before offering options
Open-ended questions
- Problem: "What should I do next?" → ambiguous
- Fix: Present exactly 4 structured options
Automatic worktree cleanup
- Problem: Remove worktree when might need it (Option 2, 3)
- Fix: Only cleanup for Options 1 and 4
No confirmation for discard
- Problem: Accidentally delete work
- Fix: Require typed "discard" confirmation
Red Flags
Never:
- Proceed with failing tests
- Merge without verifying tests on result
- Delete work without confirmation
- Force-push without explicit request
Always:
- Verify tests before offering options
- Present exactly 4 options
- Get typed confirmation for Option 4
- Clean up worktree for Options 1 & 4 only
Integration
Called by:
- subagent-driven-development (Step 7) - After all tasks complete
- executing-plans (Step 5) - After all batches complete
Pairs with:
- using-git-worktrees - Cleans up worktree created by that skill
About Superpowers
Superpowers is a complete software development workflow for your coding agents, built on top of a set of composable "skills".
Philosophy
- Test-Driven Development - Write tests first, always
- Systematic over ad-hoc - Process over guessing
- Complexity reduction - Simplicity as primary goal
- Evidence over claims - Verify before declaring success
Installation
Note: Installation differs by platform. Claude Code has a built-in plugin system. Codex and OpenCode require manual setup.
Claude Code (via Plugin Marketplace)
In Claude Code, register the marketplace first:
/plugin marketplace add obra/superpowers-marketplace
Then install the plugin from this marketplace:
/plugin install superpowers@superpowers-marketplace
Verify Installation
Check that commands appear:
/help
# Should see:
# /superpowers:brainstorm - Interactive design refinement
# /superpowers:write-plan - Create implementation plan
# /superpowers:execute-plan - Execute plan in batches
Links & Support
- Repository: https://github.com/obra/superpowers
- Issues: https://github.com/obra/superpowers/issues
강력한 Agent Skills
전문적인 스킬 컬렉션으로 AI 성능을 높이세요.
즉시 사용 가능
스킬을 지원하는 모든 에이전트 시스템에 복사하여 붙여넣으세요.
모듈형 디자인
'code skills'를 조합하여 복잡한 에이전트 동작을 만드세요.
최적화됨
각 'agent skill'은 높은 성능과 정확도를 위해 튜닝되었습니다.
오픈 소스
모든 'code skills'는 기여와 커스터마이징을 위해 열려 있습니다.
교차 플랫폼
다양한 LLM 및 에이전트 프레임워크와 호환됩니다.
안전 및 보안
AI 안전 베스트 프랙티스를 따르는 검증된 스킬입니다.
사용 방법
간단한 3단계로 에이전트 스킬을 시작하세요.
스킬 선택
컬렉션에서 필요한 스킬을 찾습니다.
문서 읽기
스킬의 작동 방식과 제약 조건을 이해합니다.
복사 및 사용
정의를 에이전트 설정에 붙여넣습니다.
테스트
결과를 확인하고 필요에 따라 세부 조정합니다.
배포
특화된 AI 에이전트를 배포합니다.
개발자 한마디
전 세계 개발자들이 Agiskills를 선택하는 이유를 확인하세요.
Alex Smith
AI 엔지니어
"Agiskills는 제가 AI 에이전트를 구축하는 방식을 완전히 바꾸어 놓았습니다."
Maria Garcia
프로덕트 매니저
"PDF 전문가 스킬이 복잡한 문서 파싱 문제를 해결해 주었습니다."
John Doe
개발자
"전문적이고 문서화가 잘 된 스킬들입니다. 강력히 추천합니다!"
Sarah Lee
아티스트
"알고리즘 아트 스킬은 정말 아름다운 코드를 생성합니다."
Chen Wei
프론트엔드 전문가
"테마 팩토리로 생성된 테마는 픽셀 단위까지 완벽합니다."
Robert T.
CTO
"저희 AI 팀의 표준으로 Agiskills를 사용하고 있습니다."
자주 묻는 질문
Agiskills에 대해 궁금한 모든 것.
네, 모든 공개 스킬은 무료로 복사하여 사용할 수 있습니다.