Run any Skill in Manus with one click

git-commit

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.

Run Skill in Manus

Stars0

Forks0

UpdatedMay 22, 2026 at 16:29

Source

Operatorr

Operatorr/vibe-translate

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

SKILL.md

readonly

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

Git Commit

Commit all current repository changes with an auto-generated message. Do not ask the user for confirmation.

Workflow

Inspect state in parallel:
- git status --short — what will be staged
- git diff --stat and git diff — the actual changes
- git log -5 --oneline — to match the repo's existing commit style
If there is nothing to commit, report that and stop. Do not create an empty commit.
Stage everything from the repository root:
- git add -A
Generate a commit message:
- Subject line is ≤ 72 characters and summarizes the change.
- Body is 2–5 sentences focused on the why more than the what.
- If the current branch name contains a task/issue number such as feature/ABC-123-name, start the subject with that number. Otherwise omit it.
- Do not include 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.

Failure handling

If a pre-commit hook modifies files, fails, or leaves staged/unstaged changes, report that state rather than silently retrying.
If a summary of the work is already in context or supplied as arguments, use it when writing the commit message.
Never include Co-Authored-By lines in commit messages.

More from this repository

same repository

code-review

Operatorr/vibe-translate

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

2026-05-220

deep-review

Operatorr/vibe-translate

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.

2026-05-220

git-pr

Operatorr/vibe-translate

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.

2026-05-220

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

Git Commit

Commit all current repository changes with an auto-generated message. Do not ask the user for confirmation.

Workflow

Inspect state in parallel:
- git status --short — what will be staged
- git diff --stat and git diff — the actual changes
- git log -5 --oneline — to match the repo's existing commit style
If there is nothing to commit, report that and stop. Do not create an empty commit.
Stage everything from the repository root:
- git add -A
Generate a commit message:
- Subject line is ≤ 72 characters and summarizes the change.
- Body is 2–5 sentences focused on the why more than the what.
- If the current branch name contains a task/issue number such as feature/ABC-123-name, start the subject with that number. Otherwise omit it.
- Do not include 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.

Failure handling

If a pre-commit hook modifies files, fails, or leaves staged/unstaged changes, report that state rather than silently retrying.
If a summary of the work is already in context or supplied as arguments, use it when writing the commit message.
Never include Co-Authored-By lines in commit messages.