git-commit
Create conventional commits from staged/unstaged changes. Use when user asks to commit, create commits, commit changes, commit all, make commits, separate commits, commit everything, stage and commit, commit these changes, save and push, commit this work, or requests push after committing. Handles single or multiple commits, staging, message generation from diffs, and push operations.
What this skill does
# Git Commit Stage changes and create conventional commits from diff analysis. ## Workflow ### 1. Gather Context ```bash git status git diff HEAD git log --oneline -10 ``` ### 2. Determine Commit Strategy **Single commit:** All changes relate to one logical change **Multiple commits:** Changes span distinct features/fixes/areas If multiple commits needed: 1. Group related changes by type and scope 2. Create separate commits for each group 3. Follow dependency order (e.g., deps before features) ### 3. Per Commit: Analyze & Stage Review diff to extract: - **Type**: feat, fix, refactor, docs, test, chore - **Scope**: module/component affected - **Description**: imperative mood summary (50-72 chars) Stage related files: ```bash git add <files-for-this-commit> ``` **Never stage:** - `.env` files - Credentials - Secrets/tokens ### 4. Create Commit Format: ``` <type>(scope): description Optional body with details ``` **Rules:** - Imperative mood: "add" not "added" - Generate from diff, not user's words - NEVER add Claude signature/co-authorship - Atomic: one logical change per commit ### 5. Repeat or Push **Multiple commits:** Return to step 3 for next commit **Push requested:** Run `git push` after all commits **No push requested:** Stop after committing ## Conventional Commit Types - `feat` - New features - `fix` - Bug fixes - `refactor` - Code restructuring without behavior change - `docs` - Documentation only - `test` - Tests - `chore` - Tooling, deps, config ## Examples **Single commit:** ``` feat(api): add user authentication endpoint Implements JWT token generation, login/logout routes, and bcrypt password hashing. ``` **Multiple commits scenario:** ``` 1. chore(deps): install jsonwebtoken and bcrypt 2. feat(auth): add JWT token signing function 3. feat(auth): add token verification middleware 4. docs(api): document authentication endpoints ```
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.