push

Git Push

Push commits to remote after validating that there are no lint, type, or build errors.

Task

Step 1: Check Current State

Verify there are commits to push:

# Check if branch has upstream
git status

# Show unpushed commits
git log @{u}..HEAD --oneline 2>/dev/null || git log --oneline -5

If there are no commits to push, report this and stop.

Step 2: Run Validation Checks

Run all validation checks. All must pass before pushing.

pnpm lint

pnpm typecheck

pnpm build

If any check fails: Stop and report the errors. Do not push.

Step 2.5: Verification Gate

After all checks pass, verify with fresh evidence:

1. Re-read the output of lint, typecheck, and build
2. Confirm zero errors in each
3. Do not push based on a previous run — the checks in Step 2 ARE the fresh evidence

Refer to the verification-before-completion skill.

Step 3: Review What Will Be Pushed

Show the commits that will be pushed:

# Show commits ahead of remote
git log @{u}..HEAD --oneline 2>/dev/null || echo "No upstream branch set"

# Show current branch
git branch --show-current

Step 4: Push to Remote

Push the current branch:

git push

If no upstream is set, push with -u flag:

git push -u origin $(git branch --show-current)

Step 5: Verify

Confirm the push was successful:

git status

Output Format

Git Push

Validation:
  [x] Lint passed
  [x] Typecheck passed
  [x] Build passed

Pushed:
  Branch: [branch-name]
  Commits: X commit(s)
  - [hash] [message]
  - [hash] [message]

Status: Successfully pushed to origin

Edge Cases

• Lint fails: Report errors, suggest fixes, do not push
• Typecheck fails: Report errors with file locations, do not push
• Build fails: Report build errors, do not push
• No upstream: Set upstream with -u origin <branch>
• Remote rejected: Report rejection reason (likely needs pull/rebase)
• No commits to push: Report "Already up to date with remote"
• Uncommitted changes: Warn user about uncommitted changes (but still push existing commits)