Git Advanced Workflows
ReviewAudited by ClawScan on May 1, 2026.
Overview
This instruction-only Git guide is coherent and purpose-aligned, but it documents powerful Git operations that should be used carefully.
This skill appears safe to install as a Git reference, but treat its commands as powerful operations. Before running rebase, reset, worktree removal, bisect automation, or force-push commands, verify the target repository and branch, keep backups where appropriate, and avoid running repository scripts from untrusted code.
Findings (2)
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.
A mistaken force-push or history rewrite could disrupt collaborators or remove expected commits from a remote branch.
The skill documents a force-push workflow that can rewrite a remote branch. This is expected for advanced Git cleanup, but it is high-impact if used on the wrong or shared branch.
# Force push cleaned branch (safe if no one else is using it) git push --force-with-lease origin feature/user-auth
Confirm the repository, remote, and branch before running history-rewriting or push commands, and ensure the branch is not shared unless the team has agreed.
Running bisect automation in an untrusted repository could execute scripts from current or historical project revisions.
Automated bisect runs local project scripts while Git checks out different commits. This is purpose-aligned debugging behavior, but it executes repository-controlled commands.
git bisect run ./test.sh ... git bisect run npm test
Use automated bisect only in repositories you trust, and inspect test scripts or package commands before allowing them to run.