Security audit
Security checks for vulnerabilities and agentic risk
This is a Git helper skill, but it includes broad activation language and under-warned commands that can permanently change or delete repository work.
Review before installing. Use this skill only for explicit Git tasks, and do not let it run destructive commands such as hard reset, force clean, history rewrite, BFG deletion, reflog expiry, or aggressive garbage collection unless you have reviewed the exact repository state, backed up needed work, and intentionally approved the command.
The activation text is broad enough to match generic coding, debugging, and deployment requests, causing the skill to activate outside narrow Git-specific contexts. In combination with exposed exec/write tools and documented destructive Git commands, this increases the chance that the agent will inappropriately steer normal development requests into repository-modifying actions.
The markdown includes destructive commands like git reset --hard, git clean -f/-fd, history rewriting, and aggressive garbage collection without prominent user-facing warnings, confirmation requirements, or safer alternatives. In an agent setting with exec/write access, this can lead to irreversible loss of uncommitted work, deletion of files, or repository history corruption if the commands are suggested or executed incautiously.
The skill documents history-rewriting repository cleanup commands, including git filter-branch with git rm --cached and BFG deletion patterns, which can permanently alter commits across all refs. In the context of an agent skill with exec capability, these parameters are dangerous because misuse can destroy audit history, remove the wrong content at scale, and complicate recovery, especially if users provide broad paths or the agent generalizes the pattern.
git clean -fd # 删除文件和目录
# ...
git filter-branch --force --index-filter \
'git rm --cached --ignore-unmatch path/to/file' \
--prune-empty --tag-name-filter cat -- --all
# ...
bfg --delete-folders folder_name
git reset --hard discards local changes and can move branch state irreversibly from the user’s perspective, especially when used by an automated agent. Because this skill exposes exec/write tools and presents the command as a recovery step without strong safeguards, there is a substantial risk of accidental data loss or repository damage.
git checkout COMMIT_ID -- file.txt
# ...
git reflog # 查找提交
git reset --hard COMMIT_ID # 恢复
# ...
git reflog # 找到分支最后的提交
git checkout -b branch_name COMMIT_ID
No suspicious patterns detected.