← Back to Skills Marketplace
124
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install proper-git-commit
Description
Smart git commit with remote sync, amend intelligence, and conventional commits. Use when the user asks to commit changes, stage and commit, "/commit", save...
Usage Guidance
This skill appears to implement a helpful commit workflow but has practical risks. Before installing or enabling it: 1) Require explicit user confirmation before any git pull/rebase or push — do not allow automatic network operations on casual mentions. 2) Remove or make optional the automatic 'git add -A' and instead present a staged-file selection to the user; ensure it never stages known secret files by default. 3) Make the inclusion of AI-model or vendor info in commit footers optional and clearly documented — this can leak runtime/model metadata to remote servers. 4) Test the skill in a disposable repository to observe behavior (especially rebase/abort flows). 5) If you do enable autonomous invocation, restrict triggers (do not trigger on every mention of 'commit' — require a command/confirmation). These changes would reduce the risk of accidental data exposure or unwanted pushes.
Capability Analysis
Type: OpenClaw Skill
Name: proper-git-commit
Version: 1.0.0
The skill provides a structured workflow for git commits, including remote synchronization, conventional commit message generation, and safety checks to avoid committing secrets (e.g., .env, .pem). It uses standard git commands and includes robust error handling, such as automatically aborting rebases on conflict, without any evidence of malicious intent or data exfiltration.
Capability Assessment
Purpose & Capability
The name/description match the git commands and flow in SKILL.md (fetch, rebase, diff, amend/new commit, generate conventional commits). However, the SKILL.md prescribes embedding agent/model info into commit footers and instructs the skill to 'TRIGGER' on any mention of committing — this aggressive trigger behavior is not reflected in the registry metadata (always:false) and feels disproportionate to a simple commit helper.
Instruction Scope
Instructions include running repository-wide commands (git fetch/pull/rebase, git add -A, git push) and rely on the agent's 'judgment' to stage changes while also telling it to avoid secrets. This is ambiguous and grants broad discretion: a blanket git add -A can stage secrets accidentally; automatic rebase/pull and push behavior can expose private data or rewrite history without an explicit, enforced confirmation step. The SKILL.md's required trigger behavior ('TRIGGER this skill whenever the user mentions committing') is overly broad and risks unintended commits or pushes.
Install Mechanism
Instruction-only skill with no install steps and no code files. Lowest installation risk — nothing is written to disk by a package mechanism.
Credentials
The skill asks the agent to append 'Co-authored-by: Claude <[email protected]>' and 'AI-model: <model-id>' using 'what's available from the environment' but declares no required environment variables. Expecting model or system context without declaring required env vars is an untracked data request. Including model identifiers and a fixed vendor email in commits may leak internal runtime metadata to remote Git servers and seems unnecessary for a generic git helper.
Persistence & Privilege
Metadata does not request always:true and the skill is user-invocable only — appropriate. However, combined with the SKILL.md's instruction to trigger on casual mentions and to perform networked operations (fetch/pull/rebase/push), autonomous invocation (the platform default) would give this skill the ability to modify and push remote repositories without strong explicit confirmation. That combination raises operational risk even though no permanent presence or special privileges are requested.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install proper-git-commit - After installation, invoke the skill by name or use
/proper-git-commit - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of smart git commit skill with remote sync and amend intelligence.
- Automatically checks and syncs with the remote branch before committing, aborting on conflicts for safety.
- Analyzes diffs to determine whether to create a new commit or amend the previous commit, using strict conventional commit rules.
- Generates standardized conventional commit messages and includes model/agent info in the commit footer.
- Stages relevant changes (excluding secrets), with built-in safety and clear user guidance on conflicts or pre-commit hook failures.
- Supports optional push when requested, with safeguards against unsafe operations.
Metadata
Frequently Asked Questions
What is Commit code safe and nice?
Smart git commit with remote sync, amend intelligence, and conventional commits. Use when the user asks to commit changes, stage and commit, "/commit", save... It is an AI Agent Skill for Claude Code / OpenClaw, with 124 downloads so far.
How do I install Commit code safe and nice?
Run "/install proper-git-commit" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Commit code safe and nice free?
Yes, Commit code safe and nice is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Commit code safe and nice support?
Commit code safe and nice is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Commit code safe and nice?
It is built and maintained by Hugo Gu (@hugogu); the current version is v1.0.0.
More Skills