Security audit
Security checks for vulnerabilities and agentic risk
This is a straightforward Git command reference skill, with some destructive Git examples that users should run only deliberately.
Installers should treat this as a useful Git reference, but agents should not run destructive examples such as git reset --hard, git clean -fdx, force pushes, stash clearing, or global config changes unless the user explicitly asks and understands the effect.
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).
git pull --rebase
# Push changes
git push
# Push new branch
git push -u origin branch-name
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).
git reset --soft HEAD~1
# Undo last commit (discard changes)
git reset --hard HEAD~1
# Revert commit (create new commit)
git revert commit-hash
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).
git reset --soft HEAD~1
# Undo last commit (discard changes)
git reset --hard HEAD~1
# Revert commit (create new commit)
git revert commit-hash
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).
git clean -fd
git clean -fdx
## Common Workflows
This markdown file includes irreversible commands such as git reset --hard HEAD~1 and git reset --hard commit-hash, which can permanently discard uncommitted or committed work. Although some nearby comments describe the effect, the skill does not provide a clear safety warning about potential data loss before presenting these commands.
The git clean -f, git clean -fd, and git clean -fdx examples perform file and directory deletion, including ignored files, but the markdown does not include a clear warning that these deletions can be irreversible. Listing a preview command (git clean -n) helps, but it is not an explicit user warning about destructive impact.
No suspicious patterns detected.