commitlisted

# Git Commit Create a well-formatted git commit using the project's commit conventions. User hint: $ARGUMENTS ## Context Current branch — run this command and read the output: ```bash git branch --show-current ``` Working tree status — run this command and read the output: ```bash git status --short ``` Staged changes (stat) — run this command and read the output: ```bash git diff --cached --stat ``` Unstaged changes (stat) — run this command and read the output: ```bash git diff --stat ``` Full diff against HEAD — run this command and read the output: ```bash git diff HEAD ``` Recent commits (for style matching) — run this command and read the output: ```bash git log --oneline -10 ``` --- ## Commit Convention Read the project's AGENTS.md and/or CLAUDE.md to discover the commit message format. Look for: - Subject line format (e.g., `Scope(type[detail]) description`, Conventional Commits `type(scope): description`, or other patterns) - Body structure (e.g., `why:/what:` sections) - Component naming conventions If no project convention is found, fall back to Conventional Commits: `type(scope): description`. Match the style of the recent commits shown above — capitalization, tense, level of detail. ### Message scope Commit messages are the canonical home for branch-internal narrative — renames, refactors, attempts-then-reverts, intermediate states, "first I tried X" stories. Put that content *here*, not in the artifacts the commit modifies (code, docstrings