SkillHub ClubShip Full StackFull Stack

commit

Create a well-formatted conventional commit

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

240

Hot score

Updated

March 20, 2026

Overall rating

C3.2

Composite score

3.2

Best-practice grade

B81.2

Install command

npx @skill-hub/cli install spirimirror-libuipc-commit

Repository

spiriMirror/libuipc

Skill path: .cursor/skills/commit

Create a well-formatted conventional commit

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: spiriMirror.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install commit into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/spiriMirror/libuipc before adding commit to shared team environments
Use commit for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: commit
description: Create a well-formatted conventional commit
disable-model-invocation: true
---

# Commit

## Overview

Create a well-formatted, conventional commit locally. **Do NOT push unless the user explicitly asks to push.**

## Steps

### 1. Format Changed Files

Run [format command](./format.md) on all changed C++ files before staging.

### 2. Stage Changes

```bash
git add <files>
```

Or stage all changes:

```bash
git add -A
```

Review what's staged:

```bash
git diff --cached --stat
```

### 3. Write Commit Message

Use a temp file to avoid shell escaping issues (`output/` is gitignored):

```bash
mkdir -p output/.cursor
```

Write the commit message to `output/.cursor/commit_msg.txt` following the [commit convention](../rules/commit-convention.mdc).

### 4. Commit

```bash
git commit -F output/.cursor/commit_msg.txt
rm -r output/.cursor
```

### 5. Push (only if user explicitly requests)

Only push when the user says "push", "commit and push", or similar. Otherwise, stop after step 4.

```bash
git push
```

If the branch has no upstream yet:

```bash
git push -u origin HEAD
```