Git Repo
WarnAudited by ClawScan on May 10, 2026.
Overview
The skill mostly matches its Git/SourceGit purpose, but its migration script can automatically rewrite or remove Git metadata in ways that may risk local repository data.
Review carefully before installing. The Git and SourceGit features are mostly disclosed, but do not run the migration or worktree-fix scripts on valuable repositories without a backup and manual status checks. Be especially cautious with the repo-to-ghq migration script, close SourceGit before preference edits, and use least-privileged GitHub credentials for multi-account cloning.
Findings (5)
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 migration could alter repository metadata or working-tree/index state and may risk staged or uncommitted work if run on an important repository.
The migration script performs destructive or state-changing filesystem/Git operations automatically after invocation, including removing Git metadata, copying/removing worktree metadata, rebuilding the index, force-checking out files, and moving the whole repository.
rm .git ... cp -R "$bare_repo" .git ... rm -rf .git/worktrees ... git read-tree HEAD ... git checkout-index -a -f ... mv "$src_path" "$new_ghq_path"
Run only after a backup, inspect the repository status before and after, prefer a dry-run/confirmation workflow, and avoid automatic read-tree or checkout-index operations unless explicitly approved.
A user may trust the guide's safety promises and run a script that does not actually follow them.
The migration guide frames cp, rm -rf, mkdir -p, and git read-tree as prohibited or dangerous, while the included migration script uses those same operations. This mismatch makes the documented safety posture unreliable.
| `cp` (instead of mv) | Original remains causing duplicates... | `rm -rf` (for cleanup) | ... | `mkdir -p` (in ghq) | ... | **Do NOT run `git read-tree HEAD`** — it destroys all staged changes.
Reconcile the documentation and script behavior before use; the skill should either remove the risky operations or clearly disclose when and why they run.
The GitHub token may grant access to private repositories and could be exposed if command lines or logs are captured.
The multi-account clone workflow reads a local GitHub CLI token and embeds it in the clone URL, then removes it from the remote afterward. This is purpose-aligned but uses account credentials.
TOKEN=$(gh auth token --user <GITHUB_USER> 2>/dev/null)
git clone "https://<GITHUB_USER>:${TOKEN}@github.com/org/repo.git" ...
git -C ... remote set-url origin "https://github.com/org/repo.git"Use the least-privileged token possible, avoid logging commands containing tokens, and prefer safer credential-helper or environment-variable approaches where available.
Cloning a repository through this workflow may also change SourceGit's saved repository list or groups.
Automatic SourceGit registration is clearly disclosed and aligned with the skill purpose, but it still mutates a persistent GUI client configuration file without an extra confirmation step.
When `ghq get <url>` is executed... Register in SourceGit... **Proceeds automatically without user confirmation**
Check that SourceGit is closed, keep a backup of preference.json, and confirm that automatic registration is desired before invoking the clone workflow.
Repository paths and possibly local change context may be handled by another skill when patrol processing is selected.
The patrol workflow delegates repository analysis to another skill by passing a repository path. This appears purpose-aligned, but the called skill's behavior is outside this artifact set.
When invoking commit-splitter, pass the repository path: /commit-splitter <repo-path>
Use this integration only if the commit-splitter skill is installed from a trusted source and its data handling is acceptable.