git-commit

Included with Lifetime

$97 forever

Create atomic, well-structured Git commits following Conventional Commits. Use when committing changes to ensure consistent commit messages with proper scoping and detailed bodies.

General

What this skill does


# Automated Git Commits

This skill provides instructions for performing atomic, well-structured Git commits following the Conventional Commits specification.

## 1. Analyze Changes
- **Identify Modified Files**: Run `git status --short` to see all staged and unstaged changes.
- **Respect Ignore Rules**: Do NOT include files that the user has explicitly requested to ignore or that match `.gitignore` patterns.
- **Group by Scope**: Group modified files by their logical "scope" (e.g., a specific module, feature, or layer like `data`, `domain`, `ui`).

## 2. Branching
- **Feature Branches**: ALWAYS create descriptive feature branches from `main` (e.g., `feat/login-logic`).
- **Merge Flow**: Merge back into `main` only after passing all quality checks and PR approval.

## 3. Generate Commit Message
- **Conventional Commits**: Each commit MUST follow the pattern: `<type>(<scope>): <message>`.
    - **Types**: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `revert`.
    - **Scope**: The module or area being changed (e.g., `auth`, `api`).
    - **Message**: A concise description in imperative mood.
- **Sub-messages (Commit Body)**:
    - ALWAYS include a detailed body if the change involves logic, breaking changes, or multiple steps.
    - Explain the "What", "Why", and "How" of the change.
    - Use blank lines to separate the subject from the body.

## 3. Atomic Commits
- **One Scope per Commit**: Perform separate commits for different scopes.
- **Stage Selectively**: Stage only the files belonging to the current scope.

## 4. Execution Flow
- **Step 1**: Group files by scope.
- **Step 2**: For each group:
    - Stage the files.
    - Generate the conventional commit message (subject + body).
    - Execute:
      ```bash
      git commit -m "<subject>" -m "<body>"
      ```
- **Step 3**: Verify history (`git log -n 5`).

Files: 1

Size: 2.1 KB

Complexity: 11/100

Category: General

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