skill-015

Push to GitHub

Category: Operations Last Updated: January 2026

---

Purpose

Automate the git workflow from staged changes to pull request creation. Ensures code quality checks run before commits, generates conventional commit messages, and creates well-documented PRs that link to related issues and specs.

---

Applies When

• User wants to push code to GitHub
• Creating a pull request
• Committing completed work
• Trigger phrases: "push to github", "create PR", "commit and push", "ready to merge", "submit changes"

---

Prerequisites

1. Git configured: git config user.name and git.config user.email set
2. On a branch: Should NOT be on main or master for feature work
3. GitHub CLI (optional): gh CLI for automated PR creation

---

Worktree Support

When working in a git worktree (e.g., spaarke-wt-{project-name}), additional sync is required:

Architecture Understanding

┌─────────────────────────────────────────────────────────────┐
│  Main Repo (C:/code_files/spaarke)                          │
│  └─ LOCAL master branch ← needs explicit pull after merge   │
├─────────────────────────────────────────────────────────────┤
│  Worktree (C:/code_files/spaarke-wt-{project})              │
│  └─ feature/work branch → pushes to origin/master           │
├─────────────────────────────────────────────────────────────┤
│  GitHub (origin/master) ← "merge to master" updates this    │
└─────────────────────────────────────────────────────────────┘

Worktree Detection

DETECT worktree:
  git rev-parse --git-common-dir

  IF output contains ".git/worktrees":
    → Working in a worktree
    → MAIN_REPO_PATH = git rev-parse --git-common-dir (parent of .git/worktrees)
    → After merge to master, MUST sync main repo

Auto-Sync After Merge (MANDATORY for Worktrees)

When merging to master from a worktree, always sync the main repo:

# After pushing branch:master
cd {MAIN_REPO_PATH}
git fetch origin
git pull origin master