semantic-gitlisted

# Semantic Git Manage Git commits using conventional commit format with atomic commits and concise messages. This skill is **zagi-aware** and is designed to work well with AI IDEs (Cursor, etc.) ## Tooling - **Preferred**: [`zagi`](https://github.com/mattzcarey/zagi) (a better git interface for agents). - Assume zagi is installed if: - `git` is aliased to zagi in the shell **or** - a `zagi` binary is available. - When in doubt, treat `git` as if it may be zagi-compatible and avoid using exotic flags. - Even when zagi is available, **generate plain `git` commands** and let any `git` → `zagi` integration handle them. - **Fallback**: plain `git` when zagi is not available. ## When to Use - Committing changes to git - Staging files for commit - Creating commit messages - Managing atomic commits - Before pushing changes ## Core Principles - **Atomic commits**: Stage and commit related changes together. Tests go with implementation code. - **User confirmation**: Always confirm with user before committing and before moving to the next commit. - **Conventional format**: Use conventional commit message format (feat, fix, etc.) unless directed otherwise. - **Concise messages**: Keep messages brief and to the point. Omit description unless change is complicated. - **Command transparency**: Always show the exact `git` commands that will be run (which may be handled by zagi via alias/wrapper), and ask whether the user wants: - to run them manually, or - to have t