commit

Included with Lifetime

$97 forever

Smart git commit with short, concise messages

General

What this skill does


## Pre-Commit Security Check

Before committing, ensure GitLeaks is configured in the project:

1. **Check for Husky setup**: Look for `.husky/pre-commit`
2. **Verify GitLeaks integration**: Check if `gitleaks protect` is in the pre-commit hook
3. **Auto-configure if missing**:
   - If `.husky/` exists but GitLeaks is missing, add `gitleaks protect --staged --verbose` before any `lint-staged` command
   - If `.husky/` doesn't exist, run `npx husky init` first, then configure GitLeaks

Example `.husky/pre-commit` with GitLeaks:
```bash
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

# Secrets detection - fail fast if secrets found
gitleaks protect --staged --verbose

# Lint staged files (if present)
npx lint-staged
```

Only proceed with the commit after confirming GitLeaks is properly configured.

---

## Language Conventions

**Infer language style from the project:**
- Analyze existing commit messages, documentation, and code comments to detect the project's language variant (US English, UK English, etc.)
- Match the spelling conventions found in the project (e.g., "organize" vs "organise", "color" vs "colour")
- Maintain consistency with the project's established language style throughout commit messages

---

Create git commits with a balanced approach - keep related changes together, split only when potentially huge:

**COMMIT MESSAGE RULE: ALWAYS use short messages (max 50 characters)**

1. Pull latest changes from remote to ensure branch is up to date (git pull)
2. Show current git status and analyse all changes
3. Check conversation context for GitHub issue references:
   - If a GitHub issue is mentioned in the conversation, determine if changes **close** the issue (complete implementation) or **relate** to it (partial work)
   - Add appropriate footer: "Closes #123" or "Relates to #123"
   - If no issue is mentioned in context, proceed without issue reference
4. Assess the scope of changes:
   - **Small to medium changes**: Keep related changes in a single commit
   - **Large changes**: Only split when the changeset is potentially huge and mixing unrelated functionality
5. For normal commits:
   - Stage all related changes together
   - Create ONE short, descriptive commit message (max 50 characters)
   - Focus on the main purpose of the change
   - Add GitHub issue footer if applicable (from step 3)
6. For huge changesets only:
   - Group by major functional areas
   - Stage files by logical groups
   - Create separate commits for distinct features/fixes

**Commit Message Requirements (ALWAYS ENFORCE):**
- **Maximum 50 characters** - no exceptions
- Use present tense verbs (add, fix, update, remove, refactor)
- Be specific but concise (e.g., "fix auth redirect bug", "add user search")
- Prefer cohesive commits over artificially split ones

This approach maintains clean git history with consistently short, readable commit messages.

Files: 1

Size: 3.1 KB

Complexity: 10/100

Category: General

Source: https://github.com/ruchernchong/claude-kit/tree/main/skills/commit

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts