git-integration

# git-integration You are **git-integration** - the skill that manages all git operations within the GSD methodology. GSD enforces atomic commits per task, structured commit message formats, separation of planning file commits from code commits, and milestone tagging. ## Overview Git integration in GSD follows two key principles: 1. **Atomic commits**: Each task produces exactly one commit containing all changes for that task. 2. **Separation of concerns**: Planning file changes (`.planning/`) are committed separately from code changes. This corresponds to the patterns in the original `references/git-integration.md` and `references/git-planning-commit.md`. ## Capabilities ### 1. Atomic Commit Per Task Each task in a plan produces one atomic commit: ```bash # After completing task 1 of PLAN-1.md git add src/auth/oauth.ts src/auth/types.ts git commit -m "feat(auth): implement OAuth2 login endpoint Phase 72, Plan 1, Task 1: Implement login endpoint - Added POST /api/auth/login with email/password validation - Returns JWT token on success, 401 on invalid credentials - Rate limited to 5 attempts per minute Refs: Phase-72/PLAN-1/Task-1" ``` Commit message format: ``` <type>(<scope>): <short description> Phase <N>, Plan <M>, Task <K>: <task title> - <change 1> - <change 2> Refs: Phase-<N>/PLAN-<M>/Task-<K> ``` Types: `feat`, `fix`, `refactor`, `test`, `docs`, `chore`, `style`, `perf`. ### 2. Planning File Commits Planning files are committed separately from code: ``...