troubleshoot-rebase
Diagnose and recover from git rebase failures
What this skill does
# Git Rebase Troubleshoot
Diagnose and recover from rebase failures. Invoke when standard rebase error handling cannot resolve the issue.
## Quick Diagnosis
Check: `pwd`, `git status`, `git branch --show-current`, `git worktree list`, `gh pr view`.
## Error: Push Rejected (Non-Fast-Forward)
Branches have diverged. First, confirm your current branch: `git branch --show-current`.
- If this is a **feature branch** (for example `feature/foo`) and the push was rejected:
- Rebase onto the latest main: `git fetch origin --force && git rebase origin/main`
- Then push your feature branch: `git push --force-with-lease origin HEAD`
- If you are on **main** and are behind `origin/main`, do **not** rebase main:
- Update main: `git fetch origin --force && git reset --hard origin/main`
- Then retry your original operation (for example, rebase your feature branch onto main and push the feature branch).
If the rebase fails because `origin/main` moved again, repeat: fetch, rebase your feature branch, then push with `--force-with-lease`.
## Error: Repository Rule Violations
GH013 error about PR/status checks. This is NOT a block if commits are from approved PR.
**Causes**: CI not passing, reviews not approved, merge conflict.
**Fix order**: Rebase feature -> push (triggers CI) -> wait for checks -> merge to main -> push.
Check: `gh pr view <branch> --json checks,reviews,statusCheckRollup`
## Error: Embedded Git Repository
Nested .git directory found. Fix: `git rm --cached <folder-name>` or add to `.gitignore`.
## Rebase Conflict
Identify: `git status`, `git diff --name-only --diff-filter=U`
Resolve: edit files, `git add <file>`, then `git rebase --continue` (or `--abort`).
## Error: Fast-Forward Merge Failed
Main was updated between rebase and merge. Run `git fetch origin --force && git reset --hard origin/main`, then retry.
## Error: Feature Branch Push Failed
Fix: `git push --force-with-lease origin <branch>`
## Recovery: Aborting In-Progress Rebase
`git rebase --abort && git status`
## Verification
Before retrying:
- Main synced: `git diff origin/main --stat` (should be empty)
- Branch clean: `git status`
- No rebase in progress: check `.git/rebase-{merge,apply}` doesn't exist
- PR state: `gh pr view <branch> --json state`
## Escalation
If unresolved: check `git reflog`, review `git log -10 --oneline`, ask user.
**DO NOT**: Use `--force` (use `--force-with-lease`), use `gh pr merge`, run `git rebase -i`.
## Related Skills
- **rebase-pr** (github-workflows) — Standard rebase-merge PR workflow this skill troubleshoots
- **troubleshoot-precommit** (git-workflows) — Troubleshoot pre-commit hook failures during rebase
- **troubleshoot-worktree** (git-workflows) — Troubleshoot git worktree, branch, and refname issues
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.