commit-msg

Included with Lifetime

$97 forever

Generate a single-line commit message from conversation context and git diff, then optionally commit

General

What this skill does

# Commit Message

Generate a single-line commit message based on the conversation context, using the git diff to confirm scope.

## Instructions

### Phase 1: Gather Context

1. Review the full conversation history — this is the primary source of intent
2. Run `git diff --staged`
- **If there is staged output, use it. Do NOT run `git diff` (unstaged). Skip to Phase 2.**
- If there is no staged output, run `git diff` to check for unstaged changes
- If neither staged nor unstaged changes exist, inform the user and stop

Only one diff should be in scope — staged takes priority. Ignore any unstaged diff output from earlier in the conversation if staged changes exist.

### Phase 2: Analyse

Priority order:

1. **Conversation intent** — what was the user trying to achieve? What problem were they solving? What did they ask for?
2. **Conversation arc** — did the approach evolve? Was there a key decision or pivot?
3. **Diff confirmation** — use the staged diff to verify scope and catch anything the conversation might not fully reflect

The conversation tells you _why_. The diff tells you _what_. Prefer _why_.

### Phase 3: Generate Message

Create a single-line commit message following these rules:

- Start with verb: add, fix, update, remove, refactor, rename, move
- Lowercase, no period at end
- Max 72 characters
- Focus on _what_ and _why_, not _how_
- Be specific: "fix login redirect loop" not "fix bug"
- Reflect the user's intent from the conversation, not just a mechanical description of changed lines

### Phase 4: Output & Commit

1. Display only the commit message, nothing else. No explanation, no alternatives.
2. Ask the user if they want to commit with this message.
- If **yes** — run `git commit -m "<message>"` (stage all tracked changes first with `git add -u` if nothing is currently staged)
- If **no** — stop. Do not commit.

Files: 1

Size: 2.0 KB

Complexity: 4/100

Category: General

Source: https://github.com/psousa50/claude-plugins/tree/main/plugins/git/skills/commit-msg

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