git-push
Internal push step for the blake-os git-ops router. Publishes local commits to origin only when the branch is current, after verifying it is not behind; never force-pushes. Invoked by blake-os:git-ops — not a direct entry point. Trigger directly only on the exact request "git push".
What this skill does
# Git Push
Publish local commits to `origin` — but only when the branch is current with the remote. If the remote moved, integrate first with `git-sync`, then push. A push is never forced.
## Prerequisites
Commit first. If the working tree has uncommitted changes, run **git-commit** or report what is still dirty.
## Workflow
### Step 1: Verify repo and remote
```bash
git remote get-url origin
git branch --show-current
```
If no `origin` remote, stop: "No remote configured. Add one with: git remote add origin <url>"
### Step 2: Fetch and measure state
```bash
git fetch origin
git rev-list --left-right --count @{u}...HEAD # output: "<behind> <ahead>"
```
The `rev-list` line prints **behind** then **ahead**. Decide on the numbers:
- **`behind = 0`, `ahead = 0`** — stop: "Already up to date with remote — nothing to push." (If `@{u}` errors because no upstream is set, the branch is new — go straight to Step 3, which sets the upstream.)
- **`behind > 0`** (the remote has commits the local branch doesn't, whether or not it is also ahead) — **stop and do not push.** Report: "Remote has N commits you don't have. Run **git-sync** first to integrate them (it will fast-forward or merge), then push." A push now would be rejected — do not attempt it.
- **`behind = 0`, `ahead > 0`** — clear to push. Continue to Step 3.
### Step 3: Push
If the branch has no upstream:
```bash
git push -u origin HEAD
```
If an upstream exists:
```bash
git push
```
**Never** `git push --force` or `--force-with-lease`.
### Step 4: Verify
```bash
git fetch origin && git rev-list --left-right --count @{u}...HEAD
```
Confirm `behind = 0, ahead = 0` — local matches remote. Report: branch, remote URL, number of commits pushed.
## Guardrails
- **Never force-push.**
- **Never push while behind** — integrate via `git-sync` first.
- **Never push secrets** — if `.env` or credential files appear in the outgoing commits, stop and warn.
- If the push is rejected for another reason (auth, pre-receive hook), report the error verbatim. Do not force.
## Order
Ordering across operations is owned by `blake-os:git-ops`.
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.