collect-commit-info

Included with Lifetime

$97 forever

Analyze staged files, group by category, and generate conventional commit specs as JSON.

Generalscripts

What this skill does


This skill analyzes staged git files and returns commit specifications as JSON. It:
1. Collects staged file metadata via script
2. Reads diff content to understand changes
3. Groups files by category (deps, ci, config, source, test, docs)
4. Generates conventional commit messages for each group
5. Returns JSON specs for the caller to execute

## Arguments

| Arg | Default | Description |
|-----|---------|-------------|
| `--lang` | context | Message language (conversation context → system locale → en) |

## Output Contract

This skill ALWAYS returns JSON. The caller executes git commands based on this output.

**Success:**
```json
{
  "commits": [
    {"message": "type(scope): subject\n\nBody", "files": ["file1", "file2"]}
  ],
  "summary": {"total_commits": 1, "total_files": 2}
}
```

**Error:**
```json
{"error": "description", "error_code": "CODE"}
```

## Workflow

### Step 1: Collect file info

```bash
${CLAUDE_PLUGIN_ROOT}/skills/collect-commit-info/scripts/collect-info.sh --lang <code>
```

Script returns JSON with `temp_dir`, `files` array (with categories), and `paths.diff_content`.

On error JSON → return it immediately and stop.

### Step 2: Read diff content

Read the file at `paths.diff_content` to understand what changed.

### Step 3: Group files by category

Group files from the `files` array. Commit order:
1. `deps` - Dependencies (package.json, lock files)
2. `ci` - CI/CD (.github/*)
3. `config` - Configuration (*.yml, *.toml, rc files)
4. `source` - Source code
5. `test` - Tests (*_test.*, *.test.*, *.spec.*)
6. `docs` - Documentation (*.md, docs/*)

### Step 4: Generate commit messages

For each group, create a conventional commit message:

```
type(scope): imperative subject (max 50 chars)

Optional body explaining what and why.
```

**Type by category:**
| Category | Type |
|----------|------|
| deps | chore |
| ci | ci |
| config | chore |
| source | feat/fix/refactor (analyze diff) |
| test | test |
| docs | docs |

**For source files, analyze diff to determine type:**
- New functionality → `feat`
- Bug fixes, error handling → `fix`
- Restructuring, cleanup → `refactor`

**Scope:** Derive from paths (e.g., `src/auth/*` → `auth`)

**Language:** Use `lang.effective` from script output. If conversation context indicates a preferred language, use that instead.

### Step 5: Cleanup and return

```bash
${CLAUDE_PLUGIN_ROOT}/skills/collect-commit-info/scripts/cleanup.sh <temp_dir>
```

Return the JSON commit specs.

Files: 3

Size: 8.0 KB

Complexity: 33/100

Category: General

Source: https://github.com/reedom/claude-code-commands/tree/main/git/skills/collect-commit-info

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