git-commit

Name: git-commit
Availability: InStock
Author: chikage0o0

Check repository state and stage changes before committing via task call.

34|6|Updated Jan 19, 2026

Search Tags:#automation #git #workflow #commit #safety #code-quality #version-control

Ready to run

npx skills add https://github.com/Chikage0o0/opencode --skill git-commit-chikage0o0

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Chikage0o0/opencode/tree/main/skills/git-commit
Command: npx skills add https://github.com/Chikage0o0/opencode --skill git-commit-chikage0o0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git submission workflows often suffer from accidental commits or insecure operations. This skill ensures that Git commits are performed only when the user explicitly requests them, preventing unintended changes and direct shell git-commit usage.

Core Features & Use Cases

仅在用户明确要求提交到 Git 时触发，避免模糊指令导致不合时宜的提交
通过 task 调用 git-commit 执行实际提交，避免直接执行 git commit
在提交前自动检查仓库状态、冲突和暂存区，并锁定提交范围
提交后校验提交标题、正文与提交范围，默认不执行 git push 典型场景包括：需要在团队工作流中强制明确的提交请求时进行提交，或在涉及敏感分支时确保额外确认。

Quick Start

明确提出要提交到 Git 时，告诉我需要提交的范围和信息，我将通过 task 调用 git-commit 以最小上下文完成提交。

Frequently Asked Questions about git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent accidental git commits in my automation workflow?▼

To prevent accidental git commits, this skill triggers submissions only when explicitly requested. It checks repository state, conflicts, and staging area before executing a safe commit via a temporary file, avoiding unintended changes.

How does this skill handle git commit safety before staging changes?▼

Git commit safety is handled by verifying the repository state, checking conflicts, and locking the commit range before execution. It uses a temporary file for the git-commit task call instead of running direct shell commands.

Can I use this skill to automatically push my git commits to a remote repository?▼

No, you cannot use this skill to automatically push commits. The git-commit skill defaults to not executing git push, ensuring changes remain local until you manually decide to push them to a remote.

What is the best way to ensure my git workflow only commits when I explicitly mean it?▼

The best way to ensure explicit git commits is using a constrained workflow that requires a direct user request. This skill validates the commit title, body, and scope while avoiding direct shell git-commit usage.

Does the git-commit skill work with sensitive branches and require extra confirmation?▼

Yes, the git-commit skill works with sensitive branches by ensuring extra confirmation. It operates within a constrained scope and uses minimal context like user request, repo path, and task scope to execute safely.

Why does my automated git workflow use a temporary file for committing instead of git commit directly?▼

An automated git workflow uses a temporary file for committing to avoid insecure direct shell operations. This method safely handles the git-commit task call with minimal context, preventing accidental or unintended submissions.