open-skills:create-commit
Create a commit from selected current changes, or show the message when commits are prohibited.
- License 许可
- MIT
- 最近更新
- 2026-10-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- open-skills:create-commit
- description
- Create a commit from selected current changes, or show the message when commits are prohibited.
03 SKILL.md 正文
Commit
Reply in {{response_language}}.
Commit all current changes.
-
Read the project instructions first. If an agent may not create commits, work message-only: never stage or commit.
-
Run
git status --short,git status,git diff, andgit diff --cached. If a merge, rebase, cherry-pick, or revert is in progress, report a conflict then stop. -
If there are no changes, say so and stop.
-
Check the state of the staging area. If there are modified or untracked files that are not yet staged, inform the user and list them. Do not add them automatically. Offer the following options:
- add specific files to the current staging area;
- add all detected changes;
- proceed with the commit using only the changes already staged;
- cancel the commit.
Wait for the user's choice before running
git add. -
Write one short imperative message for all changes in {{commit_language}}. Use
git diff --cachedafter staging, or the full working-tree changes in message-only mode. No body. -
If
{{task_prefix_regexp}}is non-empty, rungit branch --show-currentand prepend the match as<match> <message>on one line. A project-defined format wins. -
In message-only mode, show the message and stop. Else commit with
git commit -m "<message>", adding--no-verifyonly if the user asked. -
Run
git log -1 --stat. Report the commit. If it differs from what was reviewed, report and stop; do not amend.
Guards
- Never edit file contents, reset, or stash.
- Do not undo user edits to restore a previous agent result.
If git commit fails, report the error and ask:
- retry with
--no-verify; - fix issues detected by pre-commit hooks (name the cause first; this does not permit disabling hooks);
- do nothing.
Do not retry or change files until the user chooses. After a fix, reread the diffs and status before retrying.
04 同仓库更多 Skills
open-skills:track-changes
Report key changes in watched modules or files for the last day, or since Friday on Mondays, with authors and commits, in plain language.
open-skills:say-hello
A minimal test skill that greets the user.
open-skills:preview-commit
Show the change summary and proposed commit message for selected current changes without committing.
open-skills:investigate-error
Investigate crashes from a stack trace or an error-monitoring MCP reference; use diagnostic red/green tests and report evidence, root cause, impact, counts, and fix priority without applying production fixes.
open-skills:implement-task
Start implementing the current task on the current branch right away.
open-skills:explain-task
Find a task by reference through the connected MCP tracker and explain it in clear, plain language.