get-git-diff

# Git Diff Analyzer

## � MANDATORY COMPLIANCE �

**CRITICAL**: The 4-step workflow outlined in this document MUST be followed in exact order for EVERY diff analysis. Skipping steps or deviating from the procedure will result in incomplete analysis. This is non-negotiable.

## File Structure

- **SKILL.md** (this file): Main instructions and MANDATORY workflow
- **examples.md**: Usage scenarios with different diff types
- **../../context/git/**: Shared git context files
  - `git_diff_reference.md`: Unified diff format reference and best practices
  - `diff_patterns.md`: Common patterns to identify in code changes
- **../../memory/skills/get-git-diff/**: Project-specific diff analysis memory
  - `{project-name}/`: Per-project diff patterns and insights
- **scripts/**:
  - `README.md`: Complete documentation for all helper scripts
  - `validate.sh`: Git repository and commit validation functions
  - `commit_info.sh`: Commit metadata retrieval (hash, author, date, message)
  - `diff_stats.sh`: Diff statistics and line count analysis
  - `file_operations.sh`: File operation detection (add, modify, delete, rename)
  - `utils.sh`: General utilities (branch detection, formatting, repo info)
- **templates/**:
  - `output_template.md`: Standard output format template

## Analysis Focus Areas

Git diff analysis evaluates 7 critical dimensions:

1. **Change Scope**: Files affected, lines modified, overall impact radius
2. **Change Type**: Feature addition, bug fix, refactoring, configuration change
3. **Structural Changes**: File renames, moves, deletions, additions
4. **Risk Assessment**: Breaking changes, API modifications, database migrations
5. **Code Quality Impact**: Complexity changes, test coverage changes
6. **Merge Conflicts**: Merge commit analysis, conflict resolution patterns
7. **Performance Impact**: Algorithm changes, database query modifications, resource usage

**Note**: Analysis depth is summary-level, focusing on what changed and high-level impact.

---