1# Phase 3: Analyze Changes
 2
 3You are analyzing code changes to understand their nature and scope.
 4
 5## Objective
 6Produce a clear, neutral summary of what changed in the codebase.
 7
 8## Input
 9You will receive:
10- List of changed files from the triggering commit/PR
11- Repository structure from Phase 2
12
13## Instructions
14
151. **Categorize Changed Files**
16   - Source code (which crates/modules)
17   - Configuration
18   - Tests
19   - Documentation (already existing)
20   - Other
21
222. **Analyze Each Change**
23   - Review diffs for files likely to impact documentation
24   - Focus on: public APIs, settings, keybindings, commands, user-visible behavior
25
263. **Identify What Did NOT Change**
27   - Note stable interfaces or behaviors
28   - Important for avoiding unnecessary documentation updates
29
304. **Output Format**
31Produce a markdown summary:
32
33```markdown
34## Change Analysis
35
36### Changed Files Summary
37| Category | Files | Impact Level |
38| --- | --- | --- |
39| Source - [crate] | file1.rs, file2.rs | High/Medium/Low |
40| Settings | settings.json | Medium |
41| Tests | test_*.rs | None |
42
43### Behavioral Changes
44- **[Feature/Area]**: Description of what changed from user perspective
45- **[Feature/Area]**: Description...
46
47### Unchanged Areas
48- [Area]: Confirmed no changes to [specific behavior]
49
50### Files Requiring Deeper Review
51- `path/to/file.rs`: Reason for deeper review
52```
53
54## Constraints
55- Read-only: Do not modify any files
56- Neutral tone: Describe what changed, not whether it's good/bad
57- Do not propose documentation changes yet