Common workflows
Follow simple command sequences for everyday multi-repository work.
Run these examples from the folder that contains your repositories. Add --repo <path> to any supported command when you want to target one repository instead.
Check and update a workspace
git-wrangler status
git-wrangler pull --rebase
git-wrangler status
The first status check shows what is clean, changed, ahead, or behind. Pull updates local working copies, and the final check confirms the result.
Use fetch instead of pull when you only want to refresh remote information without changing working files.
Commit, review, and push changes
git-wrangler commit
git-wrangler review
git-wrangler push
commit creates one AI-generated Conventional Commit in each changed repository. review shows committed work that has not been pushed. push publishes it to origin.
Fix ignored files
git-wrangler fix-gitignore
git-wrangler untrack
git-wrangler commit
fix-gitignore adds useful ignore rules. untrack stops tracking files that are now ignored but leaves them on disk. Review the staged removals before committing.
Add license files
git-wrangler license --type mit --name "Jane Doe"
Existing LICENSE files are skipped unless you choose --overwrite. Use git-wrangler license remove when you intentionally want to remove exact root LICENSE files.
Inspect activity and history
git-wrangler activity --year 2026
git-wrangler log --summary --limit 100
activity shows when work happened. log shows the commits themselves and can filter by date, type, or scope.
Rewrite history safely
git-wrangler rewrite-authors --name "Jane Doe" --email "jane@example.com"
git-wrangler push --force
History rewrite commands preview the planned change and ask before applying it. Review History rewriting safely before using them, especially in shared repositories.