git-commit
Use when creating Git commits.
What this skill does
# Git Commit ## Staged Changes Run `git status` to see what changes are staged for commit. If there are no staged changes, stage all modified files. ## Title Create a clear, succinct title that explains what the commit accomplishes. Brief - only the essentials. **Use imperative mood:** "Add feature" not "Added feature" or "Adds feature" Good examples: - Add user authentication - Fix memory leak in parser - Update dependencies - Remove deprecated API endpoints Avoid overly detailed titles and phrases like "This commit..." or "Changes to..." ## Body **MOST COMMITS SHOULD HAVE NO BODY. DO NOT ADD A BODY UNLESS ABSOLUTELY NECESSARY.** A title-only commit is almost always better. **Before adding a body, ask yourself:** Does this body add information that isn't obvious from the title? If the body just expands on what the title already says, delete it. Bad example: ``` Add writing-markdown skill - Add SKILL.md with instructions - Add scripts/resource-paths script ``` The body just restates "Add writing-markdown skill" in more words. Delete the body. **Only add a body when the title genuinely can't capture important context.** The body must contain non-redundant detail that adds real value. **Write bodies in markdown.** Use markdown formatting for lists, emphasis, code, etc. Common patterns (only when a body is truly necessary): - **Simple context (1-2 sentences):** Explain the "why" or rationale when it's not obvious - **Bullet list:** List specific changes when there are multiple distinct items - **Paragraph + bullet list:** Provide context, then list specific changes under a "Changes:" header - **Multiple sections:** Use headers to organize complex changes (e.g., "Changes:" and "Template-specific changes:") The title says "what" - the body explains "why" or provides specific details ## Create Commit Create the commit using a heredoc to preserve formatting: ```bash git commit -m "$(cat <<'EOF' Commit title here Optional body here. EOF )" ``` ## Rationalizations | Thought | Reality | | ---------------------------------- | --------------------------------- | | "I'll provide multiple versions" | Draft ONE commit message | | "I should explain the format" | Start with the title directly | | "I'll introduce the message" | NO introductory text whatsoever | | "This simple change needs context" | Simple changes rarely need bodies | **REQUIRED:** See [references/examples.md](references/examples.md) for correct formatting.
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.