# Commit

> Stage and create git commits after showing a commit plan, with no AI attribution. Explicit-only; run only when the user invokes /commit or asks to commit, never autonomously.

- Skill: `corticalstack/commit` (Agent Skill)
- Install (CLI): `npx skillmds@latest add corticalstack/commit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/corticalstack/commit/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: corticalstack (https://skillmd.com/u/corticalstack)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/corticalstack/commit

---


# Commit Changes

You are tasked with creating git commits for the changes made during this session.

## Process:

1. **Think about what changed:**
   - Review the conversation history and understand what was accomplished
   - Run `git status` to see current changes
   - Run `git diff` to understand the modifications
   - Consider whether changes should be one commit or multiple logical commits

2. **Plan your commit(s):**
   - Identify which files belong together
   - Draft clear, descriptive commit messages
   - Use imperative mood in commit messages
   - Focus on why the changes were made, not just what

3. **Present your plan to the user:**
   - List the files you plan to add for each commit
   - Show the commit message(s) you'll use
   - Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?"

4. **Execute upon confirmation:**
   - Use `git add` with specific files (never use `-A` or `.`)
   - Create commits with your planned messages
   - Show the result with `git log --oneline -n [number]`

## Important:
- **NEVER add co-author information or Claude attribution**
- Commits should be authored solely by the user
- Do not include any "Generated with Claude" messages
- Do not add "Co-Authored-By" lines
- Write commit messages as if the user wrote them

## Remember:
- Context may have been cleared during long sessions - rely on `git status` and `git diff` to understand changes, not just conversation history
- If unsure about change intent, read the modified files or ask the user
- Group related changes together
- Keep commits focused and atomic when possible
- The user trusts your judgment - they asked you to commit