Busycommit
Create multiple atomic git commits, one logical change at a time
Claude CodeGeneric
---
description: Create multiple atomic git commits, one logical change at a time
argument-hint: [optional-commit-description]
---
## General Guidelines
### Output Style
- **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
- Write natural, descriptive code without meta-commentary about the development process
- The code should speak for itself - TDD is the process, not the product
Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues (the user interacts via `bd` commands).
Create multiple atomic git commits, committing the smallest possible logical unit at a time
Include any of the following info if specified: $ARGUMENTS
## Process
1. Run `git status` and `git diff` to review changes
2. Run `git log --oneline -5` to see recent commit style
3. Stage relevant files with `git add`
4. Create commit with descriptive message
5. Verify with `git status`
## Example
```bash
git add <files>
git commit -m "feat(#123): add validation to user input form"
Atomic Commit Approach
Each commit should represent ONE logical change. Do NOT bundle multiple unrelated changes into one commit.
- Identify the smallest atomic units of change
- For EACH atomic unit: stage only those files/hunks, commit, verify
- Use
git add -pto stage partial file changes when a file contains multiple logical changes - Repeat until all changes are committed
- It is OK to create multiple commits without stopping - keep going until
git statusshows clean
Multi-Commit Example
If a single file contains multiple unrelated changes, use git add -p to stage hunks interactively:
# Stage only the validation-related hunks from the file
git add -p src/user-service.ts
# Select 'y' for validation hunks, 'n' for others
git commit -m "feat(#123): add email format validation"
# Stage the error handling hunks
git add -p src/user-service.ts
git commit -m "fix(#124): handle null user gracefully"
# Stage remaining changes
git add src/user-service.ts
git commit -m "refactor: extract user lookup to helper"
Maintain Busycommit?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[Busycommit on getagentictools](https://getagentictools.com/loops/patreeceeo-stage-only-the-validation-related-hunks-from-the-file?ref=badge)