Menu
Stage all repository changes and create a git commit with an auto-generated message after inspecting status, diff, and recent commit style. Use when the user asks to commit changes, save changes in git, stage and commit, or create a commit without needing confirmation.
| name | git-commit |
| description | Stage all repository changes and create a git commit with an auto-generated message after inspecting status, diff, and recent commit style. Use when the user asks to commit changes, save changes in git, stage and commit, or create a commit without needing confirmation. |
| argument-hint | Optional summary of the work to commit |
Commit all current repository changes with an auto-generated message. Do not ask the user for confirmation.
Inspect state in parallel:
git status --short — what will be stagedgit diff --stat and git diff — the actual changesgit log -5 --oneline — to match the repo's existing commit styleIf there is nothing to commit, report that and stop. Do not create an empty commit.
Stage everything from the repository root:
git add -AGenerate a commit message:
feature/ABC-123-name, start the subject with that number. Otherwise omit it.Co-Authored-By lines.Commit using a HEREDOC so formatting is preserved:
git commit -m "$(cat <<'EOF'
<subject>
<body>
EOF
)"
Run git status after the commit to verify success.
Co-Authored-By lines in commit messages.Perform deep, context-aware code reviews for GitHub pull requests or local branch changes. Use when the user asks to review a PR, analyze pull request changes, review current branch changes, run automated code review, or mentions PR
Perform a maximally thorough, CodeRabbit-style code review that fans out one focused sub-agent per changed file, runs every available linter/SAST/secret scanner, and reports every issue down to nitpicks. Use when the user asks for a deep, exhaustive, thorough, or nitpick-level review, a CodeRabbit-style review, to "find everything", to "leave no stone unturned", or wants maximum coverage on a PR or branch. Optimizes for recall; some noise is acceptable. For a fast, conservative, senior-engineer review that flags only what matters, use code-review instead.
Create a feature branch off master/develop/main when needed, stage and commit all changes, push, and immediately open a pull request via the gh CLI. Use when the user asks to open a PR, ship changes, or commit and create a pull request.
