git-commit

Included with Lifetime

$97 forever

Use when inspecting local git changes, drafting or validating Conventional Commit messages, checking type or scope choices, explaining breaking changes, or creating a focused commit from the actual diff.

General

What this skill does

# Git Commit

Inspect the actual diff before writing the message. Prefer one coherent commit per intent, then map that intent to a Conventional Commits title and only add extra sections when they carry concrete information.

Read `references/conventional-commits.md` when the type is ambiguous, when you need trailers or breaking-change wording, or when the user asks for exact format details.

## Workflow

1. Inspect the exact commit contents.
Start with `git status --short`. If the user asks for a commit, inspect `git diff --cached` first; inspect `git diff` too when unstaged changes might affect the commit boundary.
2. Define the commit boundary.
Group files by one user-visible intent. If the diff mixes unrelated work, recommend splitting it into multiple commits instead of forcing one vague summary over several intents.
3. Choose the type and scope from behavior.
Pick the lowercase Conventional Commits type that best matches the dominant behavior. Add a short noun-like scope only when it adds signal.
4. Write the title in the required format.
Use `<type>[optional scope][!]: <description>`. Keep the description short, specific, and grounded in the diff.
5. Add body and footers only when they add concrete value.
Use the body for why, constraints, or tradeoffs. Add footers only for real trailers or `BREAKING CHANGE:`.
6. Keep the message aligned with the selected diff.
Do not describe unstaged changes, planned follow-up work, or unrelated cleanup that is not part of the commit.

## Decision Rules

- Prefer `feat` for a new capability and `fix` for incorrect behavior or regressions.
- Prefer `refactor` when behavior should stay the same, and `docs` when only documentation changes.
- Prefer no scope, body, or footer unless each one adds concrete signal.
- Prefer multiple commits over one vague summary when the diff contains unrelated work.
- If the user asks for validation, check both the structure and whether the wording matches the inspected diff.
- Follow repo git rules for staging and commit structure; this skill focuses on mapping the diff to the right message.
- Do not add, preserve, or generate any AI attribution trailers in commits, PRs, or messages, including `Co-authored-by`, `Generated-by`, `Created-by`, `Coding-Agent`, model names, tool names, or agent attribution footers.

## Reference

- `references/conventional-commits.md`: exact format, common types, footer rules, breaking-change wording, and examples.

Files: 3

Size: 5.3 KB

Complexity: 19/100

Category: General

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