# GIT Commit

Create git commits using Nimbalyst's interactive commit proposal widget.

- Repository: https://github.com/nimbalyst/nimbalyst (2013 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add nimbalyst/nimbalyst --skill git-commit -g -a claude-code -y`
Codex: `npx skills add nimbalyst/nimbalyst --skill git-commit -g -a codex -y`
Cursor: `npx skills add nimbalyst/nimbalyst --skill git-commit -g -a cursor -y`
Gemini CLI: `npx skills add nimbalyst/nimbalyst --skill git-commit -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add nimbalyst/nimbalyst`

## Description

Create git commits using Nimbalyst's interactive commit proposal widget. ONLY use when the user explicitly clicks "Commit with AI" button or asks for "smart commit". For regular commit requests, use standard git commands instead.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Git Commit Workflow in Nimbalyst

This skill is for the "Commit with AI" feature which provides an interactive commit proposal widget.

**IMPORTANT: Only use this when:**
- The user clicks the "Commit with AI" button (you'll see a message asking you to use developer_git_commit_proposal)
- The user explicitly asks for "smart commit" or "commit with AI"

**Do NOT use this for:**
- Generic commit requests like "commit this", "commit the changes", "make a commit"
- For those, use standard git commands: `git add` and `git commit`

## Required Steps

1. **Check if file context is already provided in the prompt**
   When the user clicks "Commit with AI", the prompt includes a pre-fetched list of session-edited files with uncommitted changes. If you see a file list in the prompt (lines like `- path/to/file.ts (modified)`), skip step 2 and go directly to step 3 using those files.

2. **Get session-edited files (fallback only)**
   Only if no file list was provided in the prompt:
   Call `mcp__nimbalyst__get_session_edited_files` to get ALL files you edited during this AI session, then cross-reference with git status.

3. **Propose the commit**
   Call `mcp__nimbalyst__developer_git_commit_proposal` with:
   - `filesToStage`: ALL session-edited files that have changes (do not cherry-pick a subset)
   - `commitMessage`: A well-crafted commit message following the guidelines below
   - `reasoning`: Explanation of why these files were selected

## Commit Message Guidelines

- Start with type prefix: `feat:`, `fix:`, `refactor:`, `docs:`, `test:`, `chore:`
- **Focus on IMPACT and WHY, not implementation details**
- Title describes user-visible outcome or bug fixed
- Use bullet points (dash prefix) only for multiple distinct changes
- Keep lines under 72 characters
- No emojis
- Lead with problem solved or capability added, not technique used

### Good vs Bad Examples

The rest: https://github.com/nimbalyst/nimbalyst/blob/HEAD/packages/extensions/developer/claude-plugin/skills/git-commit/SKILL.md