sync-branches
Sync commits to both main and v0/rohangupta-dec27c78 branches. Use after committing changes, when pushing code, or when asked to sync branches. Ensures both branches stay in lockstep.
소스 정보
- 저장소
- thisrohangupta/v0-harness-documentation-website
- 최근 소스 활동
- 2026년 3월 3일 06:12
- 감지된 SKILL.md 언어
- 영어
- 스타
- 1
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- sync-branches
- description
- Sync commits to both main and v0/rohangupta-dec27c78 branches. Use after committing changes, when pushing code, or when asked to sync branches. Ensures both branches stay in lockstep.
- disable-model-invocation
- true
- allowed-tools
- Bash(git *)
# Sync Both Branches
After committing changes, sync them to both `main` and `v0/rohangupta-dec27c78` branches. Both branches MUST always stay in sync.
## Steps
1. **Confirm current state**
- Run `git status` to ensure the working tree is clean
- Run `git log --oneline -3` to identify the commit(s) to sync
- Note the current branch
2. **If on `main`:**
```bash
git checkout v0/rohangupta-dec27c78
git cherry-pick <commit-hash>
git checkout main
```
3. **If on `v0/rohangupta-dec27c78`:**
```bash
git checkout main
git cherry-pick <commit-hash>
git checkout v0/rohangupta-dec27c78
```
4. **Push both branches:**
```bash
git push origin main
git push origin v0/rohangupta-dec27c78
```
5. **Return to the original branch** the user was on.
## Rules
- NEVER force push
- NEVER push to only one branch — both must be updated
- If cherry-pick has conflicts, stop and ask the user for guidance
- If there are uncommitted changes, stop and ask the user to commit first
- Always verify both branches have the same HEAD commit after sync
GitHub에서 보기