commit
Commit changes with smart messages. Supports full and partial commits. Use whenever committing changes or handling pre-commit hook failures.
What this skill does
# Commit ## Process 1. **Interpret arguments** — `$ARGUMENTS` could be any of: - A commit message: "refactor authentication flow" - Instructions about what to commit: "just the test files" - Empty: commit everything, generate a message Use judgment based on context. Don't ask unless unclear — infer if possible. 2. **Analyze repository state:** - `git status` — see all changes - `git diff` and `git diff --staged` — see what's changed 3. **Stage files:** - Default: stage everything (`git add .`) - If the user specified what to commit (e.g., "just the auth stuff"): stage only matching files 4. **Generate or use commit message** following these requirements: - Terse, single-line format (max ~200 characters) - NO type prefixes (no `fix:`, `feat:`, `refactor:`, etc.) - NO emojis or decorative elements - NO attribution text (no "Generated with Claude Code", no "Co-Authored-By:") - Present tense, imperative mood - Be specific about WHAT changed **Good:** `prevent race condition in session cleanup`, `rate limiting middleware` **Bad:** `fix: correct bug`, `updates`, `add new feature ✨`, `fix bug.` 5. **Commit:** ```bash git commit -m "message" ``` 6. **Handle pre-commit hook failures:** Pre-commit hooks (formatters/linters) sometimes auto-modify files during commit, causing it to fail because git won't commit when the working directory changes mid-process. - If hook **modified files** (auto-formatting): `git add .` then `git commit --amend --no-edit` - If hook **validation errors** (linting failures): report errors, do NOT retry - NEVER retry more than once — if the retry fails, investigate hook configuration - Before amending: verify authorship with `git log -1 --format='%an <%ae>'` — never amend someone else's commit 7. **Verify:** `git status` and `git log -1 --oneline`
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.