git-commit-helper
Generate well-structured git commit messages following conventional commits format. Use when committing changes, creating commit messages, or when commit history needs improvement. Ensures commits are clear, descriptive, and follow project conventions.
What this skill does
# Git Commit Helper Skill ## Instructions 1. Analyze the staged changes or diff to understand what was modified 2. Determine the type of change: - `feat`: New feature - `fix`: Bug fix - `docs`: Documentation changes - `style`: Code style changes (formatting, no logic change) - `refactor`: Code refactoring - `perf`: Performance improvements - `test`: Adding or updating tests - `chore`: Maintenance tasks, build config, etc. - `ci`: CI/CD changes - `build`: Build system changes 3. Write a clear, concise subject line (50 chars or less) 4. Add a blank line, then detailed body if needed (wrap at 72 chars) 5. Reference issues/PRs when applicable 6. Use imperative mood: "Add feature" not "Added feature" or "Adds feature" 7. Follow conventional commits format: `type(scope): subject` ## Examples **Input:** "I added a new login button and fixed the validation bug" **Output:** ``` feat(auth): add login button to header - Add new login button component to navigation header - Implement click handler to open login modal - Add styling to match design system fix(validation): resolve email validation error - Fix regex pattern for email validation - Add test cases for edge cases - Update error message to be more user-friendly Closes #123 ``` **Input:** "Updated the README and fixed some typos" **Output:** ``` docs: update README with installation instructions - Add detailed installation steps for different platforms - Include troubleshooting section - Fix typos in existing documentation ``` **Input:** "Refactored the payment processing code" **Output:** ``` refactor(payments): improve payment processing logic - Extract payment validation into separate function - Simplify retry logic for failed transactions - Improve error handling and logging - Add unit tests for payment flow BREAKING CHANGE: PaymentProcessor constructor now requires config object ``` ## Format Guidelines **Conventional Commits Format:** ``` <type>(<scope>): <subject> <body> <footer> ``` **Types:** - `feat`: New feature for users - `fix`: Bug fix for users - `docs`: Documentation only - `style`: Formatting, missing semicolons, etc. - `refactor`: Code change that neither fixes bug nor adds feature - `perf`: Performance improvement - `test`: Adding missing tests - `chore`: Changes to build process or auxiliary tools **Best Practices:** - Subject line: imperative, lowercase, no period - Body: explain what and why, not how - Footer: reference issues, breaking changes - Use present tense: "Fix bug" not "Fixed bug"
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.