Git Workflow Assistant
AdvisoryAudited by Static analysis on May 6, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If a user runs these commands in the wrong repository or branch, they could lose local work or disrupt shared Git history.
These documented Git commands can rewrite remote branch history or discard local changes. They are expected for advanced Git workflow guidance, but they require user care.
`git push --force-with-lease`; `git reset --hard HEAD~1`
Run destructive or history-rewriting Git commands only after checking `git status`, confirming the target branch, and understanding whether the branch is shared.
Global aliases affect Git usage across repositories and may surprise users later if they forget the aliases exist.
The skill suggests persistent global Git configuration changes. This is a normal Git customization pattern, not hidden background behavior, but it changes future Git behavior until removed.
git config --global alias.undo "reset --soft HEAD~1"
Only add global aliases you want permanently; use local repository config or document the change if you prefer scoped behavior.
Users cannot easily verify the author, upstream project, or update history outside the registry metadata.
The registry entry does not identify an upstream source or homepage. Because this is instruction-only with no install code, the practical supply-chain risk is low, but provenance is limited.
Source: unknown; Homepage: none
Review the included text before use and prefer skills with clear provenance when installing more powerful or executable skills.