gitview 0.1.2__tar.gz → 0.1.3__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (36) hide show
  1. {gitview-0.1.2/gitview.egg-info → gitview-0.1.3}/PKG-INFO +158 -10
  2. {gitview-0.1.2 → gitview-0.1.3}/README.md +157 -9
  3. {gitview-0.1.2 → gitview-0.1.3}/gitview/__init__.py +1 -1
  4. gitview-0.1.3/gitview/branches.py +270 -0
  5. gitview-0.1.3/gitview/cli.py +1209 -0
  6. gitview-0.1.3/gitview/index_writer.py +175 -0
  7. gitview-0.1.3/gitview/remote.py +276 -0
  8. {gitview-0.1.2 → gitview-0.1.3}/gitview/storyteller.py +200 -11
  9. {gitview-0.1.2 → gitview-0.1.3}/gitview/summarizer.py +58 -3
  10. {gitview-0.1.2 → gitview-0.1.3/gitview.egg-info}/PKG-INFO +158 -10
  11. {gitview-0.1.2 → gitview-0.1.3}/gitview.egg-info/SOURCES.txt +3 -0
  12. {gitview-0.1.2 → gitview-0.1.3}/pyproject.toml +1 -1
  13. {gitview-0.1.2 → gitview-0.1.3}/setup.py +1 -1
  14. gitview-0.1.2/gitview/cli.py +0 -665
  15. {gitview-0.1.2 → gitview-0.1.3}/INSTALL.md +0 -0
  16. {gitview-0.1.2 → gitview-0.1.3}/LICENSE +0 -0
  17. {gitview-0.1.2 → gitview-0.1.3}/MANIFEST.in +0 -0
  18. {gitview-0.1.2 → gitview-0.1.3}/bin/gitview +0 -0
  19. {gitview-0.1.2 → gitview-0.1.3}/examples/basic_usage.py +0 -0
  20. {gitview-0.1.2 → gitview-0.1.3}/gitview/backends/__init__.py +0 -0
  21. {gitview-0.1.2 → gitview-0.1.3}/gitview/backends/anthropic_backend.py +0 -0
  22. {gitview-0.1.2 → gitview-0.1.3}/gitview/backends/base.py +0 -0
  23. {gitview-0.1.2 → gitview-0.1.3}/gitview/backends/ollama_backend.py +0 -0
  24. {gitview-0.1.2 → gitview-0.1.3}/gitview/backends/openai_backend.py +0 -0
  25. {gitview-0.1.2 → gitview-0.1.3}/gitview/backends/router.py +0 -0
  26. {gitview-0.1.2 → gitview-0.1.3}/gitview/chunker.py +0 -0
  27. {gitview-0.1.2 → gitview-0.1.3}/gitview/extractor.py +0 -0
  28. {gitview-0.1.2 → gitview-0.1.3}/gitview/writer.py +0 -0
  29. {gitview-0.1.2 → gitview-0.1.3}/gitview.egg-info/dependency_links.txt +0 -0
  30. {gitview-0.1.2 → gitview-0.1.3}/gitview.egg-info/entry_points.txt +0 -0
  31. {gitview-0.1.2 → gitview-0.1.3}/gitview.egg-info/not-zip-safe +0 -0
  32. {gitview-0.1.2 → gitview-0.1.3}/gitview.egg-info/requires.txt +0 -0
  33. {gitview-0.1.2 → gitview-0.1.3}/gitview.egg-info/top_level.txt +0 -0
  34. {gitview-0.1.2 → gitview-0.1.3}/requirements.txt +0 -0
  35. {gitview-0.1.2 → gitview-0.1.3}/setup.cfg +0 -0
  36. {gitview-0.1.2 → gitview-0.1.3}/verify_installation.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: gitview
3
- Version: 0.1.2
3
+ Version: 0.1.3
4
4
  Summary: Git history analyzer with LLM-powered narrative generation
5
5
  Home-page: https://github.com/carstenbund/gitview
6
6
  Author: GitView Contributors
@@ -44,6 +44,12 @@ Dynamic: requires-python
44
44
 
45
45
  # GitView
46
46
 
47
+ [![Github-CI][github-ci]][github-link]
48
+ [![Coverage Status][codecov-badge]][codecov-link]
49
+ [![PyPI][pypi-badge]][pypi-link]
50
+ [![PyPI - Downloads][install-badge]][install-link]
51
+
52
+
47
53
  **Git history analyzer with LLM-powered narrative generation**
48
54
 
49
55
  GitView extracts your repository's git history and uses AI to generate compelling narratives about how your codebase evolved. Instead of manually reading through thousands of commits, get a comprehensive story of your project's journey.
@@ -55,17 +61,30 @@ Example run on this repository:
55
61
 
56
62
  ## Features
57
63
 
58
- - ** Comprehensive History Extraction**: Extracts commit metadata, LOC changes, language breakdown, README evolution, comment analysis, and more
59
- - ** Smart Chunking**: Automatically divides history into meaningful "phases" or "epochs" based on significant changes
60
- - ** LLM-Powered Summaries**: Uses Claude to generate narrative summaries for each phase
61
- - ** Global Story Generation**: Combines phase summaries into executive summaries, timelines, technical retrospectives, and deletion stories
62
- - ** Multiple Output Formats**: Generates markdown reports, JSON data, and timelines
64
+ - **Comprehensive History Extraction**: Extracts commit metadata, LOC changes, language breakdown, README evolution, comment analysis, and more
65
+ - **Smart Chunking**: Automatically divides history into meaningful "phases" or "epochs" based on significant changes
66
+ - **LLM-Powered Summaries**: Uses Claude to generate narrative summaries for each phase
67
+ - **Global Story Generation**: Combines phase summaries into executive summaries, timelines, technical retrospectives, and deletion stories
68
+ - **Multiple Output Formats**: Generates markdown reports, JSON data, and timelines
69
+ - **Critical Examination Mode**: Objective assessment focused on gaps, technical debt, and alignment with project goals (perfect for project leads)
63
70
 
64
71
  ## Installation
65
72
 
66
- ### Option 1: Install with pip (recommended)
73
+ ### Option 1: Install from PyPI (recommended)
74
+
75
+ Install the published package directly from PyPI to add the `gitview` command to your PATH:
76
+
77
+ ```bash
78
+ pip3 install gitview
79
+
80
+ # Confirm the CLI is available
81
+ gitview --version
82
+ gitview --help
83
+ ```
67
84
 
68
- This creates a `gitview` command in your PATH:
85
+ ### Option 2: Install from source (editable)
86
+
87
+ This installs directly from the repository in editable mode so local changes take effect immediately:
69
88
 
70
89
  ```bash
71
90
  # Clone the repository
@@ -82,7 +101,7 @@ gitview --help
82
101
 
83
102
  **How it works:** The `pip install -e .` command reads `pyproject.toml` and `setup.py`, which define an entry point that creates `/usr/local/bin/gitview` (or similar on Windows) that calls `gitview.cli:main`.
84
103
 
85
- ### Option 2: Run directly from repo (no installation)
104
+ ### Option 3: Run directly from repo (no installation)
86
105
 
87
106
  Use the executable wrapper in `bin/`:
88
107
 
@@ -103,7 +122,7 @@ export PATH="$PWD/bin:$PATH"
103
122
  gitview analyze
104
123
  ```
105
124
 
106
- ### Option 3: Run as Python module
125
+ ### Option 4: Run as Python module
107
126
 
108
127
  ```bash
109
128
  # Install dependencies
@@ -159,6 +178,9 @@ gitview analyze --backend openai
159
178
  # Using local Ollama (no API key needed)
160
179
  gitview analyze --backend ollama --model llama3
161
180
 
181
+ # Critical examination mode (for project leads)
182
+ gitview analyze --critical --todo GOALS.md
183
+
162
184
  # Skip LLM summarization (just extract and chunk)
163
185
  gitview analyze --skip-llm
164
186
  ```
@@ -185,6 +207,9 @@ Options:
185
207
  --ollama-url TEXT Ollama API URL (default: http://localhost:11434)
186
208
  --repo-name TEXT Repository name for output
187
209
  --skip-llm Skip LLM summarization (extract and chunk only)
210
+ --todo PATH Path to goals/todo file for critical examination mode
211
+ --critical Enable critical examination mode (focus on gaps and issues)
212
+ --directives TEXT Additional plain text directives for LLM analysis
188
213
  ```
189
214
 
190
215
  ### Extract Only
@@ -203,6 +228,85 @@ Chunk an extracted JSONL file into phases:
203
228
  gitview chunk history.jsonl --output ./phases --strategy adaptive
204
229
  ```
205
230
 
231
+ ## Critical Examination Mode
232
+
233
+ For project leads who need objective assessment rather than celebratory narratives, GitView offers a critical examination mode that focuses on gaps, technical debt, and alignment with project goals.
234
+
235
+ ### What Changes in Critical Mode?
236
+
237
+ **Tone & Focus:**
238
+ - Removes flowery, achievement-focused language
239
+ - Emphasizes objective assessment over celebration
240
+ - Focuses on gaps, issues, and misalignments
241
+ - Identifies what's missing or incomplete
242
+
243
+ **Analysis:**
244
+ - Evaluates progress against stated objectives
245
+ - Highlights incomplete features and technical debt
246
+ - Questions architectural decisions objectively
247
+ - Identifies delays and resource misalignment
248
+ - Notes concerning patterns and risks
249
+
250
+ ### Usage
251
+
252
+ **Basic Critical Mode:**
253
+ ```bash
254
+ gitview analyze --critical
255
+ ```
256
+
257
+ **With Project Goals/TODO File:**
258
+ ```bash
259
+ # Create a goals file (e.g., GOALS.md)
260
+ cat > GOALS.md <<EOF
261
+ # Project Goals Q1 2025
262
+ - Implement user authentication system
263
+ - Add API rate limiting
264
+ - Improve test coverage to 80%
265
+ - Migrate from SQLite to PostgreSQL
266
+ - Complete API documentation
267
+ EOF
268
+
269
+ # Analyze against goals
270
+ gitview analyze --critical --todo GOALS.md
271
+ ```
272
+
273
+ **With Custom Directives:**
274
+ ```bash
275
+ # Add specific analysis focus
276
+ gitview analyze --critical \
277
+ --todo GOALS.md \
278
+ --directives "Focus on security vulnerabilities and performance bottlenecks"
279
+ ```
280
+
281
+ **Combined Example:**
282
+ ```bash
283
+ # Critical assessment with all options
284
+ gitview analyze \
285
+ --critical \
286
+ --todo PROJECT_ROADMAP.md \
287
+ --directives "Emphasize testing gaps and code quality issues" \
288
+ --output ./critical-review
289
+ ```
290
+
291
+ ### Output in Critical Mode
292
+
293
+ The LLM will generate:
294
+
295
+ 1. **Critical Executive Summary** - Assesses progress against goals, identifies gaps and delays
296
+ 2. **Critical Timeline** - Highlights goal alignment/misalignment per phase
297
+ 3. **Critical Technical Assessment** - Identifies architectural flaws and technical debt
298
+ 4. **Critical Deletion Analysis** - Notes incomplete cleanup and lingering technical debt
299
+ 5. **Comprehensive Critical Assessment** - Full project review with actionable insights
300
+
301
+ ### When to Use Critical Mode
302
+
303
+ - **Project Reviews**: Objective assessment of development progress
304
+ - **Technical Audits**: Identify technical debt and architectural issues
305
+ - **Goal Alignment**: Measure actual work against stated objectives
306
+ - **Resource Planning**: Understand where effort was spent vs. planned
307
+ - **Risk Assessment**: Identify concerning patterns and project risks
308
+ - **Leadership Reports**: Provide factual assessment to stakeholders
309
+
206
310
  ## Chunking Strategies
207
311
 
208
312
  GitView supports three chunking strategies:
@@ -333,6 +437,30 @@ gitview chunk history.jsonl --strategy adaptive --output ./adaptive-phases
333
437
  gitview chunk history.jsonl --strategy fixed --chunk-size 25 --output ./fixed-phases
334
438
  ```
335
439
 
440
+ ### Critical Project Assessment
441
+
442
+ ```bash
443
+ # Create a goals file for your project
444
+ cat > PROJECT_GOALS.md <<EOF
445
+ # Q1 2025 Objectives
446
+ - Complete user authentication with OAuth2
447
+ - Implement API rate limiting (1000 req/hour)
448
+ - Achieve 80% test coverage
449
+ - Migrate database to PostgreSQL
450
+ - Document all public APIs
451
+ EOF
452
+
453
+ # Run critical analysis
454
+ gitview analyze \
455
+ --critical \
456
+ --todo PROJECT_GOALS.md \
457
+ --directives "Focus on security issues and incomplete features" \
458
+ --output ./project-review-q1
459
+
460
+ # Review the critical assessment
461
+ cat ./project-review-q1/history_story.md
462
+ ```
463
+
336
464
  ## Architecture
337
465
 
338
466
  ```
@@ -452,6 +580,7 @@ gitview analyze --backend openai --api-key "your-key"
452
580
 
453
581
  ## Use Cases
454
582
 
583
+ ### Standard Mode (Celebratory Narrative)
455
584
  - **Technical Documentation**: Automatically generate project history documentation
456
585
  - **Onboarding**: Help new developers understand codebase evolution
457
586
  - **Retrospectives**: Review what worked and what didn't
@@ -459,6 +588,14 @@ gitview analyze --backend openai --api-key "your-key"
459
588
  - **Code Archaeology**: Understand why code evolved the way it did
460
589
  - **Cleanup Planning**: Identify what to remove based on deletion history
461
590
 
591
+ ### Critical Examination Mode
592
+ - **Project Leadership**: Objective assessment for project leads and managers
593
+ - **Technical Audits**: Identify technical debt and architectural issues
594
+ - **Goal Tracking**: Measure actual progress against roadmap objectives
595
+ - **Resource Analysis**: Understand where development effort was spent
596
+ - **Risk Management**: Identify concerning patterns and project risks
597
+ - **Stakeholder Reports**: Provide factual, critical assessment to executives
598
+
462
599
  ## Contributing
463
600
 
464
601
  Contributions welcome! Please open an issue or submit a pull request.
@@ -466,3 +603,14 @@ Contributions welcome! Please open an issue or submit a pull request.
466
603
  ## License
467
604
 
468
605
  MIT License - see LICENSE file for details
606
+
607
+
608
+
609
+ [github-ci]: https://github.com/carstenbund/gitview/actions/workflows/tests.yml/badge.svg?branch=master
610
+ [github-link]: https://github.com/carstenbund/gitview
611
+ [pypi-badge]: https://img.shields.io/pypi/v/gitview.svg
612
+ [pypi-link]: https://pypi.org/project/gitview
613
+ [codecov-badge]: https://codecov.io/gh/carstenbund/gitview/branch/master/graph/badge.svg
614
+ [codecov-link]: https://codecov.io/gh/carstenbund/gitview
615
+ [install-badge]: https://img.shields.io/pypi/dw/gitview?label=pypi%20installs
616
+ [install-link]: https://pypistats.org/packages/gitview
@@ -1,5 +1,11 @@
1
1
  # GitView
2
2
 
3
+ [![Github-CI][github-ci]][github-link]
4
+ [![Coverage Status][codecov-badge]][codecov-link]
5
+ [![PyPI][pypi-badge]][pypi-link]
6
+ [![PyPI - Downloads][install-badge]][install-link]
7
+
8
+
3
9
  **Git history analyzer with LLM-powered narrative generation**
4
10
 
5
11
  GitView extracts your repository's git history and uses AI to generate compelling narratives about how your codebase evolved. Instead of manually reading through thousands of commits, get a comprehensive story of your project's journey.
@@ -11,17 +17,30 @@ Example run on this repository:
11
17
 
12
18
  ## Features
13
19
 
14
- - ** Comprehensive History Extraction**: Extracts commit metadata, LOC changes, language breakdown, README evolution, comment analysis, and more
15
- - ** Smart Chunking**: Automatically divides history into meaningful "phases" or "epochs" based on significant changes
16
- - ** LLM-Powered Summaries**: Uses Claude to generate narrative summaries for each phase
17
- - ** Global Story Generation**: Combines phase summaries into executive summaries, timelines, technical retrospectives, and deletion stories
18
- - ** Multiple Output Formats**: Generates markdown reports, JSON data, and timelines
20
+ - **Comprehensive History Extraction**: Extracts commit metadata, LOC changes, language breakdown, README evolution, comment analysis, and more
21
+ - **Smart Chunking**: Automatically divides history into meaningful "phases" or "epochs" based on significant changes
22
+ - **LLM-Powered Summaries**: Uses Claude to generate narrative summaries for each phase
23
+ - **Global Story Generation**: Combines phase summaries into executive summaries, timelines, technical retrospectives, and deletion stories
24
+ - **Multiple Output Formats**: Generates markdown reports, JSON data, and timelines
25
+ - **Critical Examination Mode**: Objective assessment focused on gaps, technical debt, and alignment with project goals (perfect for project leads)
19
26
 
20
27
  ## Installation
21
28
 
22
- ### Option 1: Install with pip (recommended)
29
+ ### Option 1: Install from PyPI (recommended)
30
+
31
+ Install the published package directly from PyPI to add the `gitview` command to your PATH:
32
+
33
+ ```bash
34
+ pip3 install gitview
35
+
36
+ # Confirm the CLI is available
37
+ gitview --version
38
+ gitview --help
39
+ ```
23
40
 
24
- This creates a `gitview` command in your PATH:
41
+ ### Option 2: Install from source (editable)
42
+
43
+ This installs directly from the repository in editable mode so local changes take effect immediately:
25
44
 
26
45
  ```bash
27
46
  # Clone the repository
@@ -38,7 +57,7 @@ gitview --help
38
57
 
39
58
  **How it works:** The `pip install -e .` command reads `pyproject.toml` and `setup.py`, which define an entry point that creates `/usr/local/bin/gitview` (or similar on Windows) that calls `gitview.cli:main`.
40
59
 
41
- ### Option 2: Run directly from repo (no installation)
60
+ ### Option 3: Run directly from repo (no installation)
42
61
 
43
62
  Use the executable wrapper in `bin/`:
44
63
 
@@ -59,7 +78,7 @@ export PATH="$PWD/bin:$PATH"
59
78
  gitview analyze
60
79
  ```
61
80
 
62
- ### Option 3: Run as Python module
81
+ ### Option 4: Run as Python module
63
82
 
64
83
  ```bash
65
84
  # Install dependencies
@@ -115,6 +134,9 @@ gitview analyze --backend openai
115
134
  # Using local Ollama (no API key needed)
116
135
  gitview analyze --backend ollama --model llama3
117
136
 
137
+ # Critical examination mode (for project leads)
138
+ gitview analyze --critical --todo GOALS.md
139
+
118
140
  # Skip LLM summarization (just extract and chunk)
119
141
  gitview analyze --skip-llm
120
142
  ```
@@ -141,6 +163,9 @@ Options:
141
163
  --ollama-url TEXT Ollama API URL (default: http://localhost:11434)
142
164
  --repo-name TEXT Repository name for output
143
165
  --skip-llm Skip LLM summarization (extract and chunk only)
166
+ --todo PATH Path to goals/todo file for critical examination mode
167
+ --critical Enable critical examination mode (focus on gaps and issues)
168
+ --directives TEXT Additional plain text directives for LLM analysis
144
169
  ```
145
170
 
146
171
  ### Extract Only
@@ -159,6 +184,85 @@ Chunk an extracted JSONL file into phases:
159
184
  gitview chunk history.jsonl --output ./phases --strategy adaptive
160
185
  ```
161
186
 
187
+ ## Critical Examination Mode
188
+
189
+ For project leads who need objective assessment rather than celebratory narratives, GitView offers a critical examination mode that focuses on gaps, technical debt, and alignment with project goals.
190
+
191
+ ### What Changes in Critical Mode?
192
+
193
+ **Tone & Focus:**
194
+ - Removes flowery, achievement-focused language
195
+ - Emphasizes objective assessment over celebration
196
+ - Focuses on gaps, issues, and misalignments
197
+ - Identifies what's missing or incomplete
198
+
199
+ **Analysis:**
200
+ - Evaluates progress against stated objectives
201
+ - Highlights incomplete features and technical debt
202
+ - Questions architectural decisions objectively
203
+ - Identifies delays and resource misalignment
204
+ - Notes concerning patterns and risks
205
+
206
+ ### Usage
207
+
208
+ **Basic Critical Mode:**
209
+ ```bash
210
+ gitview analyze --critical
211
+ ```
212
+
213
+ **With Project Goals/TODO File:**
214
+ ```bash
215
+ # Create a goals file (e.g., GOALS.md)
216
+ cat > GOALS.md <<EOF
217
+ # Project Goals Q1 2025
218
+ - Implement user authentication system
219
+ - Add API rate limiting
220
+ - Improve test coverage to 80%
221
+ - Migrate from SQLite to PostgreSQL
222
+ - Complete API documentation
223
+ EOF
224
+
225
+ # Analyze against goals
226
+ gitview analyze --critical --todo GOALS.md
227
+ ```
228
+
229
+ **With Custom Directives:**
230
+ ```bash
231
+ # Add specific analysis focus
232
+ gitview analyze --critical \
233
+ --todo GOALS.md \
234
+ --directives "Focus on security vulnerabilities and performance bottlenecks"
235
+ ```
236
+
237
+ **Combined Example:**
238
+ ```bash
239
+ # Critical assessment with all options
240
+ gitview analyze \
241
+ --critical \
242
+ --todo PROJECT_ROADMAP.md \
243
+ --directives "Emphasize testing gaps and code quality issues" \
244
+ --output ./critical-review
245
+ ```
246
+
247
+ ### Output in Critical Mode
248
+
249
+ The LLM will generate:
250
+
251
+ 1. **Critical Executive Summary** - Assesses progress against goals, identifies gaps and delays
252
+ 2. **Critical Timeline** - Highlights goal alignment/misalignment per phase
253
+ 3. **Critical Technical Assessment** - Identifies architectural flaws and technical debt
254
+ 4. **Critical Deletion Analysis** - Notes incomplete cleanup and lingering technical debt
255
+ 5. **Comprehensive Critical Assessment** - Full project review with actionable insights
256
+
257
+ ### When to Use Critical Mode
258
+
259
+ - **Project Reviews**: Objective assessment of development progress
260
+ - **Technical Audits**: Identify technical debt and architectural issues
261
+ - **Goal Alignment**: Measure actual work against stated objectives
262
+ - **Resource Planning**: Understand where effort was spent vs. planned
263
+ - **Risk Assessment**: Identify concerning patterns and project risks
264
+ - **Leadership Reports**: Provide factual assessment to stakeholders
265
+
162
266
  ## Chunking Strategies
163
267
 
164
268
  GitView supports three chunking strategies:
@@ -289,6 +393,30 @@ gitview chunk history.jsonl --strategy adaptive --output ./adaptive-phases
289
393
  gitview chunk history.jsonl --strategy fixed --chunk-size 25 --output ./fixed-phases
290
394
  ```
291
395
 
396
+ ### Critical Project Assessment
397
+
398
+ ```bash
399
+ # Create a goals file for your project
400
+ cat > PROJECT_GOALS.md <<EOF
401
+ # Q1 2025 Objectives
402
+ - Complete user authentication with OAuth2
403
+ - Implement API rate limiting (1000 req/hour)
404
+ - Achieve 80% test coverage
405
+ - Migrate database to PostgreSQL
406
+ - Document all public APIs
407
+ EOF
408
+
409
+ # Run critical analysis
410
+ gitview analyze \
411
+ --critical \
412
+ --todo PROJECT_GOALS.md \
413
+ --directives "Focus on security issues and incomplete features" \
414
+ --output ./project-review-q1
415
+
416
+ # Review the critical assessment
417
+ cat ./project-review-q1/history_story.md
418
+ ```
419
+
292
420
  ## Architecture
293
421
 
294
422
  ```
@@ -408,6 +536,7 @@ gitview analyze --backend openai --api-key "your-key"
408
536
 
409
537
  ## Use Cases
410
538
 
539
+ ### Standard Mode (Celebratory Narrative)
411
540
  - **Technical Documentation**: Automatically generate project history documentation
412
541
  - **Onboarding**: Help new developers understand codebase evolution
413
542
  - **Retrospectives**: Review what worked and what didn't
@@ -415,6 +544,14 @@ gitview analyze --backend openai --api-key "your-key"
415
544
  - **Code Archaeology**: Understand why code evolved the way it did
416
545
  - **Cleanup Planning**: Identify what to remove based on deletion history
417
546
 
547
+ ### Critical Examination Mode
548
+ - **Project Leadership**: Objective assessment for project leads and managers
549
+ - **Technical Audits**: Identify technical debt and architectural issues
550
+ - **Goal Tracking**: Measure actual progress against roadmap objectives
551
+ - **Resource Analysis**: Understand where development effort was spent
552
+ - **Risk Management**: Identify concerning patterns and project risks
553
+ - **Stakeholder Reports**: Provide factual, critical assessment to executives
554
+
418
555
  ## Contributing
419
556
 
420
557
  Contributions welcome! Please open an issue or submit a pull request.
@@ -422,3 +559,14 @@ Contributions welcome! Please open an issue or submit a pull request.
422
559
  ## License
423
560
 
424
561
  MIT License - see LICENSE file for details
562
+
563
+
564
+
565
+ [github-ci]: https://github.com/carstenbund/gitview/actions/workflows/tests.yml/badge.svg?branch=master
566
+ [github-link]: https://github.com/carstenbund/gitview
567
+ [pypi-badge]: https://img.shields.io/pypi/v/gitview.svg
568
+ [pypi-link]: https://pypi.org/project/gitview
569
+ [codecov-badge]: https://codecov.io/gh/carstenbund/gitview/branch/master/graph/badge.svg
570
+ [codecov-link]: https://codecov.io/gh/carstenbund/gitview
571
+ [install-badge]: https://img.shields.io/pypi/dw/gitview?label=pypi%20installs
572
+ [install-link]: https://pypistats.org/packages/gitview
@@ -1,3 +1,3 @@
1
1
  """GitView - Git history analyzer with LLM-powered narrative generation."""
2
2
 
3
- __version__ = "0.1.2"
3
+ __version__ = "0.1.3"