.agents

Workflow

1. Run these commands in parallel to understand the current state:
2. git status — see all tracked/untracked files and staging state
3. git diff — see unstaged changes

1. Analyze ALL changes (staged + unstaged) and determine what should be committed:
2. If there are no changes at all, inform the user and stop
3. Do NOT commit files that likely contain secrets (.env, credentials, tokens, API keys). Warn the user if such files are present.

1. Group related file changes into logical commits:
2. Do NOT lump all changes into a single commit
3. Examine each changed file and understand what it does
4. Group files that are part of the same logical change together (e.g., a component + its styles + its test = one commit)
5. Each group becomes its own commit
6. If only one logical change exists, one commit is fine

1. For each group, draft a commit message:
2. Write natural, concise descriptions of what changed and why
3. Do NOT use conventional commits format (no feat:, fix:, chore: prefixes)
4. Keep the subject line under 72 characters
5. If the user provided a message or instructions via arguments, incorporate or use that for the relevant commit(s)

1. For each group, stage and commit:
2. git add <specific files> for that group only
3. git commit -m "message"
4. Repeat for each group in a logical order (foundational changes first)

1. Run git status after all commits to verify everything is clean.

1. Report the result: show each commit hash and summary.

User Arguments

$ARGUMENTS