Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Contextual Git-Committer
v1.0.0AI-powered Git assistant that analyzes staged changes and terminal history to craft meaningful, conventional commit messages.
⭐ 1· 37·0 current·0 all-time
byPeter Lum@liverock
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
Name/description match the implementation: the code gathers staged diffs, recent commits, changed files, parses diff hunks, and reads terminal history to produce context for commit message suggestions. Reading terminal history is explicitly described in SKILL.md, but it is a potentially disproportionate source of context (it can contain sensitive commands or secrets) relative to the stated goal of crafting commit messages.
Instruction Scope
SKILL.md instructs the tool to read ~/.bash_history and ~/.zsh_history and the handler implements this. That behavior is visible and intentional, but it expands the scope beyond purely repository-local data: terminal history can include sensitive content (commands containing tokens, passwords, or other secrets). The instructions and handler also cause the full staged diff to be emitted (possibly including secrets), which will be provided to whatever LLM the agent uses—this is a privacy/exfiltration risk even if no network code is present in the skill itself.
Install Mechanism
No install spec or external downloads; the skill is instruction-only plus a small local Python handler. No remote installers or archive extraction are used.
Credentials
The skill requests no environment variables, credentials, or config paths beyond reading common shell history files (explicitly documented). There are no unrelated or excessive env/credential demands.
Persistence & Privilege
always is false and the skill does not request persistent/always-on privileges or modify other skills or system configs. It runs only when invoked.
What to consider before installing
This skill does what it says: it reads staged git diffs, recent commits, and your shell history to build context for commit messages. The main risk is privacy: your shell history and staged diffs can contain secrets (API keys, passwords, tokens, or sensitive commands). If you run this skill, be aware the collected context will be printed and then provided to the agent/LLM that generates messages. Before installing or invoking it:
- Review handler.py (included) and confirm you are comfortable with it reading ~/.bash_history and ~/.zsh_history.
- Avoid running it in environments where your shell history contains sensitive commands, or clear/trim those history files first.
- Consider modifying the handler to skip terminal history or to filter/sanitize history entries (or to limit to certain safe commands).
- Be cautious about staged diffs that may include secrets—inspect diffs before staging or use git-secrets/tools to pre-scan.
If you need minimal exposure, prefer a version that only reads the staged diff and recent commits (no shell history), or run the tool locally with an LLM that does not send data to an external service. If you want me to, I can suggest a safe modification to handler.py to disable or sanitize history reading.Like a lobster shell, security has layers — review code before you run it.
latestvk97dtrjnb0y0j4ayxetpg79q8s84shnz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.