Security audit
Security checks for vulnerabilities and agentic risk
This is a straightforward Chinese Git workflow reference, but users should be careful because it includes destructive Git cleanup and reset commands.
Install only if you want a Git command reference. Before running commands from it, verify the target repository and branch, prefer dry-run or backup steps, and treat reset --hard, git clean -f, filter-branch, remote branch deletion, and pushes to main/staging/production as potentially destructive.
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
# 2. 开发并提交
git add .
git commit -m "feat: 添加登录功能"
git push origin feature/login
# 3. 创建 Pull Request
# 4. Code Review
git reset --hard HEAD~1 is a destructive parameterization of a powerful tool that can delete local work immediately. In an agent skill, presenting this command without guardrails can cause accidental data loss if a user follows it without understanding that both index and working tree changes may be discarded.
git reset --soft HEAD~1
# 撤销最近提交（丢弃修改）
git reset --hard HEAD~1
# 修改最近提交信息
git commit --amend -m "新信息"
Using git reset --hard COMMIT_ID to restore deleted commits rewrites the current branch and forces the working tree to match the target commit, which can wipe out current local changes and detach users from later history if misunderstood. In documentation meant for broad developer use, this is dangerous when not paired with warnings, recovery notes, or safer restoration patterns.
# 恢复删除的提交
git reflog # 查找提交
git reset --hard COMMIT_ID # 恢复
# 恢复删除的分支
git reflog # 找到分支最后的提交
The skill documents git reset --hard HEAD~1, which irreversibly discards uncommitted changes and rewrites the working tree without any prominent warning, confirmation step, or safer alternative first. In an agent-assistance context, users may copy commands verbatim, so omission of data-loss warnings materially increases the chance of accidental destructive use.
The repository-cleaning section includes destructive commands such as git clean -f, git clean -fd, history-rewriting via git filter-branch, and aggressive garbage collection, but does not clearly warn that these can permanently delete files and alter repository history. In a workflow skill, these commands are especially risky because they are operational guidance likely to be executed directly by users.
No suspicious patterns detected.