tool-gitlisted

<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. --> # tool-git ## When To Use - Inspect working tree state and commit history. - Review and stage focused diffs before commit. - Compare branches and verify what changed. ## Trusted Commands ```bash git status --short git --no-pager diff git --no-pager diff --staged git --no-pager log --oneline -n 20 git --no-pager show HEAD git add path/to/file git restore --staged path/to/file ``` ## Safe Defaults - Use `--no-pager` in non-interactive contexts. - Stage only task-relevant files. - Check status before and after edits to avoid accidental scope creep. ## Common Pitfalls - Mixing unrelated edits into one commit. - Using destructive reset/checkout patterns without explicit approval. - Misreading staged vs unstaged columns in short status output. ## Output Interpretation - `??` indicates untracked files. - Left/right `M` columns in short status represent index/worktree changes. ## Why It Matters For Agents - Git state determines safe automation and review boundaries. - High-signal diff workflows prevent accidental regressions. ## Commit Identity (per remote host) - Commits must carry the identity that matches the remote; set it **per repo**, not globally. Leaving the global `user.email` unset is deliberate — with no email git silently commits a `…@hostname.local` address, which pollutes and de-anonymizes history. - Before committing, verify `git config user.email` is set for