git
Git operations for committing, pushing, and opening PRs using gh CLI. Use when performing version control tasks. This skill should be used when the user asks to "commit", "push", "create a PR", "ship code", "git status", or mentions git workflow, version control, or pull requests.
What this skill does
<essential_principles> <git_safety> **Never run destructive commands without explicit user request:** - No `git push --force` to main/master - No `git reset --hard` - No `--no-verify` flag (skip hooks) - No `git commit --amend` on pushed commits **Never push directly to main/master:** - If current branch is `main` or `master`, create a new branch before committing/pushing - Use a descriptive branch name based on the changes (e.g., `fix/login-bug`, `feat/add-filter`) - Only push to feature/fix branches, never directly to the default branch **Always verify before acting:** - Check `git status` before staging - Check `git log` for commit style - Check remote tracking before push </git_safety> <commit_format> End all commit messages with: ``` 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]> ``` Use HEREDOC for multi-line messages: ```bash git commit -m "$(cat <<'EOF' Message here 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]> EOF )" ``` </commit_format> <pr_format> PR body structure: ```markdown ## Summary <1-3 bullet points> ## Test plan - [ ] Test item 1 - [ ] Test item 2 🤖 Generated with [Claude Code](https://claude.com/claude-code) ``` </pr_format> </essential_principles> <intake> What would you like to do? 1. **Commit** - Stage and commit changes 2. **Push** - Push commits to remote 3. **PR** - Open a pull request 4. **Ship** - Full workflow: commit + push + PR **Wait for response before proceeding.** </intake> <routing> | Response | Workflow | |----------|----------| | 1, "commit", "stage" | `workflows/commit.md` | | 2, "push", "upload" | `workflows/push.md` | | 3, "pr", "pull request", "open pr" | `workflows/pr.md` | | 4, "ship", "full", "all" | Run commit → push → pr sequentially | **After reading the workflow, follow it exactly.** </routing> <workflows_index> | Workflow | Purpose | |----------|---------| | commit.md | Stage changes and create commit with proper message | | push.md | Push commits to remote, create branch if needed | | pr.md | Create pull request with gh CLI | </workflows_index>
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.