git-commit

Included with Lifetime

$97 forever

Use when creating git commits or pull requests, or when asked to write a commit message

General

What this skill does


# Git Commit Messages

## Overview

Write commit messages and PR descriptions with clear subject lines, explanatory
bodies, and optional trailers. Be autonomous when intent is clear, interactive
when clarification needed.

## Commit Message Format

### Subject Line

- Separate from body with blank line
- Limit to 50 characters
- Start with lowercase tag + colon: `cli:`, `rfd:`, `api:`, `db:`, `release:`
- Capitalize first word after tag
- Imperative mood ("Add feature" not "Added feature")
- No period at end

### Body

- Wrap at 72 characters
- Explain "what" and "why", not "how"
- Prose over bullet lists (bullets only when truly needed)
- May use markdown like `backticks` for code/commands
- Include verbatim commands when changes were generated (`go generate`,
  `protoc`)

### Do NOT

- Use semantic commits (`feat:`, `fix:`, `chore:`)
- Add "Generated by Claude" or co-author trailers
- End subject with period

### Example

```
rfd: Update with recent decision to drop DMS

After extensive testing, AWS DMS showed no benefits over logical
replication while being less stable and slower. The production CLI
will use logical replication only, with cluster_name instead of
tenant_id for easier tenant identification.
```

## Trailers

Add at end of body when relevant:

| Trailer         | Purpose                                  |
| --------------- | ---------------------------------------- |
| `link:`         | Reference URL for context                |
| `issue:`        | GitHub issue being addressed             |
| `poc:`          | Proof of concept repository/URL          |
| `gen-command:`  | Command that generated changes           |
| `commit-group:` | Groups related commits that could be one |

### Example with Trailers

```
api: Add user permissions endpoint

Adds GET /api/v1/users/{id}/permissions for fetching effective
permissions. Required for the new RBAC dashboard.

issue: https://github.com/org/repo/issues/123
gen-command: go generate ./pkg/api/...
```

## Interactive vs Autonomous

### Autonomous (just write the message) when:

- Single file or tightly related files changed
- Tag obvious from paths (`rfd/` -> `rfd:`, `cmd/cli/` -> `cli:`)
- Purpose clear from diff or conversation context

### Interactive (ask questions) when:

- Changes span multiple unrelated areas
- Multiple valid tags could apply
- The "why" isn't clear
- Large refactor where intent matters
- Need to split generated vs manual changes

### Questions to Ask

1. What tag best describes this change?
2. What's the motivation behind this change?
3. Should this be split into multiple commits?
4. Any trailers to add?

## PR Descriptions

### Title

Same as commit subject: ~50 chars, tag prefix, imperative mood, no period.

### Body

```
## Summary
<1-3 sentences explaining the "why">

## Test plan
<How to verify — manual steps, test commands, etc.>
```

### Optional Sections

- `## Breaking changes` — if any
- `## Related` — links to issues, RFDs, other PRs

### Do NOT

- Add "Generated by Claude" footers
- Use bullet lists in summary unless truly needed

Files: 1

Size: 3.1 KB

Complexity: 5/100

Category: General

Source: https://github.com/juliaogris/skills/tree/main/git-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