Git
A comprehensive skill catalog for AI agents
npx -y skills add G1Joshi/Agent-Skills --skill gitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Git version control with branching, merging, and rebasing. Use for source control.
SKILL.md
1.1 KB, as published. Nobody here has run it
Git
Git is the foundation of modern software. In 2025, features like Sparse Checkout and Scalar (for monorepos) are becoming mainstream.
When to Use
- Always: Use it for everything. Text files, config, code.
- Bisect: Finding bugs by binary search.
Core Concepts
Graph
Commits form a DAG (Directed Acyclic Graph).
Rebase vs Merge
- Merge: Preserves history, creates bubbles.
- Rebase: Rewrites history, linearizes.
Worktrees
Checkout multiple branches of the same repo in different folders simultaneously.
Best Practices (2025)
Do:
- Use
git switch/git restore: The modern alternatives to the overloadedgit checkout. - Use
git maintenance: Speed up fetch/clone in the background. - Sign Commits: Use SSH keys to sign commits (
Commit Signing).
Don't:
- Don't force push to shared branches:
git push --force-with-leaseis the safer alternative.
References
Gives 0 of the 12 instructions most pr commit review skills give
Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06
- use conventional commits formatin 123 of 888, across 110 files
- keep subject line under 72 charactersin 60 of 888, across 46 files
- delete branches after mergein 50 of 888, across 37 files
- use imperative mood in subject linein 50 of 888, across 41 files
- use imperative mood in commit messagesin 45 of 888
- generate a conventional commit messagein 42 of 888
- make atomic commitsin 37 of 888, across 25 files
- run tests before committingin 36 of 888, across 24 files
- run project test suite to verify clean baselinein 35 of 888, across 7 files
- run detected project setup commandsin 34 of 888, across 6 files
- wrap commit body at 72 charactersin 32 of 888, across 25 files
- split unrelated changes into separate commitsin 32 of 888, across 27 files
Said here and by no other author read
- use git for all text files
- use git switch over git checkout
- run git maintenance to speed up fetches
- use scalar for monorepos
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.