ワンクリックでManusで任意のスキルを実行

git-commit

スター3

フォーク0

更新日2026年1月23日 04:45

Iteratively, commit atomic changes to the respository. Use when the user or agent needs to autonomously commit atomic changes to the repository. Employs the "git-add", "git-message", and "git-status" in skills in sequence to perform the commit.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

mystilleef

mystilleef/llm-agent-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Commit changes in the git repository

GOAL: use the git-add, git-message and git-status skills in sequence to commit changes in the repository and clean it.

WHEN: use when the user or agent needs to commit changes in the repository.

NOTE: Await user approval of commit messages before committing. Make commits only after the user has approved the commit message.

Workflow

Follow these steps in sequence:

Step 1: Stage atomic changes

Invoke the git-add skill.
Capture the status from skill output (SUCCESS, WARN, or ERROR).
Handle the status:
- If ERROR: Halt and report the error to the user.
- If WARN (no files available): Skip to Step 5.
- If SUCCESS (files staged): Continue to Step 2.

Step 2: Generate commit message and await approval

Invoke the git-message skill.
Capture the status from skill output (APPROVED, REJECTED_EDIT_FILES, REJECTED_REGENERATE, REJECTED_ABORT, or ERROR).
Handle the status:
- If ERROR: Halt and report the error to the user.
- If APPROVED: Continue to Step 3.
- If REJECTED_EDIT_FILES: Unstage all files with git restore --staged ., then loop back to Step 1.
- If REJECTED_REGENERATE: Loop back to Step 2.
- If REJECTED_ABORT: Halt and report abort to the user.

Step 3: Commit changes

IMPORTANT: To avoid a recursive loop, DON'T invoke the git-commit skill here.

Without using the git-commit skill, perform a direct commit with git using the approved message.
If success: report the commit SHA and continue to Step 4.
If failure: Halt and report the error to the user.

Step 4: Check for more commits (automatic loop control)

Run git status --porcelain=v2 to check for remaining changes.
If no changes: Continue to Step 5.
If changes remain: automatically loop back to Step 1 (no user prompt needed).

Step 5: Present final status

Invoke the git-status skill.
DONE

Efficiency directives

Optimize all operations for agent, token, and context efficiency
Batch operations on file groups, avoid individual file processing
Use parallel execution when possible
Target only relevant files
Reduce token usage

このリポジトリの他の Skills

同じリポジトリ

git-status

mystilleef/llm-agent-skills

Present the status of the git repository to the user. Use to display the status of the repository after a successful git commit by the agent. The agent should not use this internally for its own needs.

2026-01-273

fix-markdown

mystilleef/llm-agent-skills

Fix lint, formatting, and prose issues in markdown files using Prettier and Vale. Use when the user or agent needs to fix lint, formatting, and prose issues in markdown files.

2026-01-233

git-add

mystilleef/llm-agent-skills

Autonomously select files to stage for an atomic Git commit. Use when the agent wants to stage selected files for a git commit. Only stages selected files, but does not commit them.

2026-01-233

git-message

mystilleef/llm-agent-skills

Generate a commit message for changes already in the Git staging area, and await approval from the user. Use when the agent needs to generate a commit message for staged changes. Only generates the commit message, but does not perform the commit.

2026-01-233

new-agent-skill

mystilleef/llm-agent-skills

Creates a new agent skill. Use when agent or user needs to create a new skill for the agent.

2026-01-233

cleanup-changelog

mystilleef/llm-agent-skills

Format changelog and remove empty sections.

2026-01-203

Commit changes in the git repository

GOAL: use the git-add, git-message and git-status skills in sequence to commit changes in the repository and clean it.

WHEN: use when the user or agent needs to commit changes in the repository.

NOTE: Await user approval of commit messages before committing. Make commits only after the user has approved the commit message.

Workflow

Follow these steps in sequence:

Step 1: Stage atomic changes

Invoke the git-add skill.

Capture the status from skill output (SUCCESS, WARN, or ERROR).

Handle the status:

If ERROR: Halt and report the error to the user.
If WARN (no files available): Skip to Step 5.
If SUCCESS (files staged): Continue to Step 2.

Step 2: Generate commit message and await approval

Invoke the git-message skill.

Capture the status from skill output (APPROVED, REJECTED_EDIT_FILES, REJECTED_REGENERATE, REJECTED_ABORT, or ERROR).

Handle the status:

If ERROR: Halt and report the error to the user.
If APPROVED: Continue to Step 3.
If REJECTED_EDIT_FILES: Unstage all files with git restore --staged ., then loop back to Step 1.
If REJECTED_REGENERATE: Loop back to Step 2.
If REJECTED_ABORT: Halt and report abort to the user.

Step 3: Commit changes

IMPORTANT: To avoid a recursive loop, DON'T invoke the git-commit skill here.

Without using the git-commit skill, perform a direct commit with git using the approved message.

If success: report the commit SHA and continue to Step 4.

If failure: Halt and report the error to the user.

Step 4: Check for more commits (automatic loop control)

Run git status --porcelain=v2 to check for remaining changes.

If no changes: Continue to Step 5.

If changes remain: automatically loop back to Step 1 (no user prompt needed).

Step 5: Present final status

Invoke the git-status skill.

DONE

Efficiency directives

Optimize all operations for agent, token, and context efficiency

Batch operations on file groups, avoid individual file processing

Use parallel execution when possible

Target only relevant files

Reduce token usage

name	git-commit
description	Iteratively, commit atomic changes to the respository. Use when the user or agent needs to autonomously commit atomic changes to the repository. Employs the "git-add", "git-message", and "git-status" in skills in sequence to perform the commit.