git branch --show-current

Current Branch?
    │
    ├─ main → ❌ DO NOT work here
    │         → Create a new branch first (see "Creating a New Branch")
    │
    ├─ Feature branch for this task → ✅ Continue working
    │
    └─ Different feature branch → ⚠️ Ask user which branch to use

# 1. Ensure main is up to date
git fetch origin
git reset --hard origin/main

# 2. Create new branch
git checkout -b {type}/issue-{number}-{description}

$ git branch --show-current
main
# → Must create new branch before any work!

$ git branch --show-current
feature/issue-123-add-taproot
# → OK to continue if this is the correct branch for the task

git fetch origin
git checkout main
git reset --hard origin/main
git checkout -b {type}/issue-{number}-{brief-description}

❌ 禁止パターン:
  issue-123 → fix/issue-123-first-attempt
            → fix/issue-123-second-attempt  ← これは作らない
            → fix/issue-123-another-fix     ← これも作らない

✅ 正しいパターン:
  issue-123 → fix/issue-123-description
            → PR作成 → レビュー → マージ
            → (必要なら) 新しいissueで新しいbranch

# 1. 既存のブランチを確認
git branch -a | grep "issue-{number}"

# 2. 既存のPRを確認
gh pr list --search "issue-{number}"

{type}({scope}): {brief description}

- {detail 1}
- {detail 2}

Closes #{issue_number}

feat(btc)!: change address format to bech32m only
fix!: remove deprecated API endpoint

# Feature with scope
git commit -m "feat(btc): add taproot address support

- Add bech32m encoding
- Update address validation

Closes #123"

# Bug fix without scope
git commit -m "fix: resolve database connection timeout

- Increase pool timeout
- Add retry logic

Closes #456"

# Documentation
git commit -m "docs: update architecture guide

- Add layer diagram
- Clarify dependency rules

Closes #789"

# Breaking change
git commit -m "feat(btc)!: require bech32m for all taproot addresses

BREAKING CHANGE: Legacy address format no longer supported

Closes #999"

ERROR: Commit message does not follow Conventional Commits format.

Expected format: <type>(<scope>): <description>

Types: feat, fix, docs, refactor, test, ci, chore, build, perf, style, revert

Examples:
  feat(btc): add taproot address support
  fix: resolve database connection timeout
  docs: update architecture guide
  refactor(api): reorganize endpoint handlers

Your commit message: <your-invalid-commit-message>

After commits are pushed, ALWAYS ask:
> "Would you like me to create a PR? Or is there additional work to do?"

git push -u origin {branch-name}

# Ask user: "Would you like me to create a PR?"
# Only proceed if user confirms

gh pr create --title "{type}: {description}" --body "$(cat <<'EOF'
## Summary
- {change 1}
- {change 2}

## Test plan
- [ ] Verification commands pass
- [ ] Manual testing completed

Closes #{issue_number}
EOF
)"

{type}: {description} (Closes #{issue_number})

## Summary
- Brief description of changes

## Changes
- Change 1
- Change 2

## Test plan
- [ ] Unit tests pass
- [ ] Integration tests pass (if applicable)
- [ ] Manual testing completed

## Related
- Closes #{issue_number}
- Related to #{other_issue}

# 0. 既存ブランチ/PRを確認（必須）
git branch -a | grep "issue-{number}"
gh pr list --search "issue-{number}"
# → 既存があれば、そのbranchで作業を継続

# 1. Update main
git fetch origin && git checkout main && git reset --hard origin/main

# 2. Create branch (既存がない場合のみ)
git checkout -b {type}/issue-{number}-{description}

# 3. Make changes...

# 4. Self-Review (REQUIRED - see "Pre-Commit Self-Review" section)
#    - Run verification commands for modified file types
#    - Complete self-review checklist from language skill
#    - Confirm no linter errors

# 5. Commit (only after self-review is complete)
git add <files>
git commit -m "{type}: {description}

Closes #{number}"

# 6. Push
git push -u origin {branch-name}

# 7. Ask user before creating PR (REQUIRED)
#    "Would you like me to create a PR? Or is there additional work?"
#    Only create PR if user confirms
gh pr create --title "{type}: {description}"

# Already on PR branch

# 1. Make fixes...

# 2. Self-Review (REQUIRED)
#    Run verification commands & complete checklist

# 3. Commit and push
git add <files>
git commit -m "fix(pr): address review comments"
git push