commit

Commit It

Automates the full commit workflow: inspect changes, format code, stage files, generate a Conventional Commit message, and commit. Designed to be fast — the user said "commit it" because they want it done, not to answer a bunch of questions.

Instructions

1. Check Git State

First, make sure the repo is in a clean state for committing:

git status

If the repo is in the middle of a merge, rebase, or cherry-pick, inform the user and stop. These need to be resolved manually.

If there are no changes (nothing modified, nothing untracked), tell the user "Nothing to commit" and stop.

2. Inspect Changes

Run in parallel to understand what changed:

• git diff (unstaged changes to tracked files)
• git diff --cached (already staged changes)
• git status --porcelain (all changes including untracked files — look for ?? lines)
• git log --oneline -5 (recent commits for style reference)

Important: Untracked files (?? in git status) are often newly created files from the current session. They MUST be included in the commit alongside modified files.

3. Pre-Commit Formatting

Only run formatters relevant to the files that actually changed. Collect the full list of files to commit:

# Modified tracked files (staged + unstaged)
git diff --name-only
git diff --name-only --cached
# Untracked files (newly created)
git ls-files --others --exclude-standard

If any .sol files under contracts/tests/ changed:

forge fmt <those-files>

If any .sol files NOT under contracts/tests/ changed:

npx prettier --write --plugin=prettier-plugin-solidity <those-files>

If any files under src/js/ or JS config files changed:

yarn lint --fix
yarn prettier --write <changed-js-files>

Do NOT run formatters on the entire project — only pass the specific changed files.

If formatting fails and can't auto-fix, tell the user what's wrong and ask whether to proceed anyway.

4. Stage Files