commit
Write a commit message and create a git commit. Use when the user wants to commit changes, asks for a commit message, or says "commit this" or "make a commit".
What this skill does
# Commit You are helping the user create a git commit with a well-crafted commit message. ## Workflow 1. Run these commands in parallel: - `git status` - See staged and unstaged files - `git diff --cached` - See staged changes - `git diff` - See unstaged changes - `git log --oneline -10` - See recent commit message style 2. Analyze the changes: - Understand what changed (new feature, bug fix, refactor, docs, etc.) - Identify the scope/area affected - Determine the "why" behind the changes 3. Draft a commit message following these principles: - **First line**: Concise summary (50 chars or less, imperative mood) - **Format**: `type: brief description` or just `brief description` - **Types**: feat, fix, refactor, docs, test, chore, style - **Match the repo's style**: Look at recent commits and follow their convention - **Focus on "why"**: Not just what changed, but why it matters - **No fluff**: Skip obvious details, be direct 4. Stage any relevant unstaged files if needed (ask user first if unclear) 5. Create the commit: ```bash git commit -m "$(cat <<'EOF' Your commit message here. Additional details if needed. EOF )" ``` 6. CRITICAL: Run `git status` after committing to verify success ## Important Rules - **NEVER** include `Co-Authored-By:` in the commit message - **NEVER** add co-author tags or attribution lines - **DO NOT** push to remote unless explicitly asked - **DO NOT** use `--amend` unless explicitly requested - **DO NOT** commit files with secrets (.env, credentials, etc.) - Use HEREDOC format for multi-line messages - Keep it simple and focused ## Examples of Good Commit Messages ``` feat: add dark mode toggle to settings fix: prevent crash when API returns null user refactor: extract validation logic into separate module docs: update API authentication examples test: add coverage for edge cases in parser ``` ## Style Matching Match the repository's commit style by examining `git log`. Common patterns: - Conventional commits: `type(scope): description` - Imperative mood: "add feature" not "added feature" - Sentence case vs lowercase - With/without type prefixes - Single line vs multi-line Adapt to what you observe in the recent history.
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.