push
Intelligent workflow orchestrator that commits, pushes, and creates/updates PRs automatically. Use when user wants to save their work or create a PR.
What this skill does
# /push - Git Workflow Orchestrator Handles the complete git workflow: commit → push → create/update PR. ## Workflow ### 1. Validate Current Branch (CRITICAL - do first) ```bash git branch --show-current ``` - If on staging/main/production/master: **STOP and error** - cannot commit to protected branches - If on feature branch: Continue ### 2. Handle Uncommitted Changes Check for changes: ```bash git status ``` If changes exist: 1. Review what files changed 2. Stage appropriate files (prefer specific files over `git add .`) 3. Create commit with conventional format: - `feat(scope): description` - new feature - `fix(scope): description` - bug fix - `chore(scope): description` - maintenance - `docs(scope): description` - documentation - `refactor(scope): description` - code restructure - `test(scope): description` - tests Run pre-commit checks: - No secrets/API keys in code - No debug console.log statements - No commented-out code blocks ### 3. Push to Remote ```bash # Check for unpushed commits git log origin/$(git branch --show-current)..HEAD # Push (set upstream if new branch) git push origin $(git branch --show-current) # or for new branches: git push -u origin $(git branch --show-current) ``` ### 4. Handle Pull Request Check if PR exists: ```bash gh pr list --head $(git branch --show-current) ``` **If no PR exists**: Launch `git-pr-manager` agent to create PR - Target staging/develop (not main/master) - Generate description from commits - Include summary and test instructions **If PR exists**: Report that PR was updated with new commits ### 5. Provide Summary Report: - What was committed - What was pushed - PR status (created/updated) - PR URL - Next steps ## Usage ``` /push # Commit all changes with auto-generated message /push "add auth feature" # Commit with specific message ``` ## Important Rules - **NEVER commit to protected branches** (staging, main, production, master) - Always validate branch first - Use conventional commit format - Target staging/develop for PRs (not main) - Don't stage sensitive files (.env, credentials)
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.