What problem does it solve? Recording local git history safely is error-prone: careless staging sweeps in secrets or build artifacts, commits land on the wrong branch, and risky experiments pollute the main checkout. This Skill enforces a disciplined inspect-then-commit workflow and provides isolated worktrees for speculative work. ## Core Features & Use Cases - State Inspection: Use git_status, git_diff (staged or unstaged), and git_log to see exactly what changed and what will be recorded before committing. - Disciplined Committing: Follow a staged-diff-first workflow that produces why-focused commit messages matching the repository's existing style, while avoiding the add_all trap that sweeps in secrets and large files. - Isolated Worktrees: Use git_worktree_enter and git_worktree_exit to run risky refactors or dependency upgrades in a separate worktree without touching the main checkout. - Use Case: Before committing a bug fix, run git_status, read the staged diff, write an imperative message explaining why, then confirm with git_log that the commit landed as intended. ## Quick Start Show me the current git status and staged diff, then commit my changes with a message explaining why the fix was needed.