git-commit
Pass
Audited by Gen Agent Trust Hub on May 11, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: The skill implements a proactive security measure by scanning for sensitive files such as .env, credentials, and private keys. It specifically warns the user and excludes these files from commits by default unless an explicit override is provided.
- [SAFE]: Instructions strictly prohibit the use of unsafe Git operations like
git add .orgit add -A. Instead, the skill mandates using explicit file paths to prevent accidental staging of sensitive or unrelated data. - [SAFE]: The history rewrite workflow includes multi-layered safety checks. It detects if commits have already been pushed to a remote repository and presents a clear decision menu (Cancel, Force-push, or safe Branch-based rewrite) rather than performing destructive actions silently.
- [COMMAND_EXECUTION]: The skill performs standard Git operations and executes a local Python helper script (
rewrite_msg.py) for commit message mapping. These commands are executed within the expected scope of a version control tool and use HEREDOC formatting to prevent shell injection during commit message generation. - [SAFE]: The skill adheres to the 'Least Privilege' principle by refusing to bypass pre-commit hooks or GPG signing requirements without explicit user consent.
Audit Metadata