# Commit Chunks

> Review and commit changes in meaningful chunks. Use when the user has multiple uncommitted changes that should be organized into logical, atomic commits.

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

---


# Commit Chunks

Review and commit changes in meaningful chunks.

## Instructions

1. Run `git status` and `git diff` to see all uncommitted changes
2. Review each changed file and understand what was modified
3. Group related changes into logical commits (e.g., by feature, by file type, by purpose)
4. For each group:
   - Stage only the relevant files with `git add <files>`
   - Create a commit with a clear, descriptive message following conventional commits (feat, fix, chore, docs, refactor, style, test)
5. After all commits, show `git log --oneline -10` to display the results

## Commit Message Format

```
<type>(<scope>): <description>

[optional body]
```

Examples:

- `feat(studio): add branding to graph controls`
- `fix(cli): resolve path issue in static file serving`
- `chore: update gitignore for docs folder`

## Guidelines

- Keep commits atomic (one logical change per commit)
- Don't mix unrelated changes in the same commit
- Write commit messages that explain WHY, not just WHAT
- If unsure about grouping, ask for clarification