git add
tool judged 11% likely a named technique or architecture
See how it has spread across media tiers
Mentions over time
Table view
| Week | Articles | Sources |
|---|---|---|
| 2026-W08 | 1 | 1 |
| 2026-W40 | 3 | 3 |
| 2026-W41 | 1 | 1 |
In their words
You do this once per machine: git config --global user.name "Your Name" git config --global user.email "you@example.com" Then commit: git add -A git commit -m "First version of the to-do page" From now on the repository has a commit to branch from.
git add -A swept another session's edits into the wrong commit; explicit paths don't help, since git commit takes the whole index.
As a permissions config: { "permissions": { "allow": ["Read","Edit","Write","Grep","Glob", "Bash(git add:*)","Bash(git commit:*)", "Bash(npm test:*)","Bash(npm run:*)","Bash(npm ci:*)","Bash(pytest:*)"], "ask": ["Bash(git push:*)","Bash(npm publish:*)","Bash(aws:*)","Bash(terraform apply:*)","Bash(kubectl apply:*)"], "deny": ["Bash(git push --force:*)","Bash(git push -f:*)","Bash(*--no-verify*)"]
The implementer loop runs the test suite before committing — and git add -A doesn't know the difference between your code and the __pycache__ directories the test run just created.
Try asking your agent: "run the deploy checklist." Step 4: Share it Push your skill to GitHub and anyone can install it: # From inside the skill directory git init && git add .