# Commit Staged

Should be used when user asks to "commit these changes", "write commit message", "stage...

- Repository: https://github.com/fcakyon/claude-codex-settings (1195 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

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

## Description

This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".

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

# Commit Staged

Complete workflow for creating commits following project standards.

When explicitly invoked with extra text, treat that text as additional context about the
changes and include it in commit planning and commit messages.
When session history includes findings, motivation, or rationale, include the strongest
points in the commit message body instead of relying on the diff alone.

## Process

**First, run the `/simplify` skill on the staged diff and apply its findings before committing. Docs-only diffs are a no-op.**

1. **Preferred execution**
   - If subagents are available, use `github-dev:commit-creator` for the full workflow.
   - Pass along any extra invocation text as additional context.
   - Otherwise follow the manual steps below.

2. **Analyze staged files only**
   - Check all staged files: `git diff --cached --name-only`
   - Read diffs: `git diff --cached`
   - Completely ignore unstaged changes

3. **Commit message format**
   - First line: `{type}: brief description` (max 50 chars)
   - Types: `feat`, `fix`, `refactor`, `docs`, `style`, `test`, `build`
   - Use plain language. Avoid jargon, buzzwords, and repo shorthand unless an exact command or tool name is needed.
   - Use findings and motivation from session history when available.
   - Focus on 'why' not 'what'
   - 1 sentence conventional style + 1-2 short motivation/findings sentences if possible
   - For complex changes, add bullet points after blank line

4. **Message examples**
   - `feat: add sign-in flow`
   - `fix: stop duplicate jobs on save`
   - `docs: add skills install snippets`

5. **Documentation update**
   - Check README.md for:
     - New features that should be documented
     - Outdated descriptions no longer matching implementation
     - Missing setup instructions for new dependencies
   - Update as needed based on staged changes

The rest: https://github.com/fcakyon/claude-codex-settings/blob/HEAD/plugins/github-dev/skills/commit-staged/SKILL.md