kodo 0.6.2

A CLI tool for analyzing Git commit statistics with TUI visualization
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83

# Versioning Guide

## Semantic Versioning

kodo follows [Semantic Versioning 2.0.0](https://semver.org/).

### Version Format: MAJOR.MINOR.PATCH

| Type | Example | Description |
|------|---------|-------------|
| MAJOR | 1.0.0 → 2.0.0 | Breaking changes (no API compatibility) |
| MINOR | 0.5.0 → 0.6.0 | New features (backwards compatible) |
| PATCH | 0.5.0 → 0.5.1 | Bug fixes and performance improvements only |

### 0.x.x Era (Current)

0.x.x means "in development" - API stability is not guaranteed before 1.0.0.

| Version | Allowed Changes |
|---------|-----------------|
| 0.MINOR.0 | New features + minor breaking changes |
| 0.MINOR.PATCH | Bug fixes, documentation, performance improvements only |

### 1.0.0 Release Criteria

- Core features are complete
- API is stable
- Documentation is comprehensive

## Release Flow

1. Develop on feature branch
2. Create PR → merge to main
3. Update CHANGELOG.md
4. Run `/kodo-release` skill
5. GitHub Release auto-generated

## GitHub Issues Workflow

### Labels

| Label | Purpose |
|-------|---------|
| `enhancement` | New feature |
| `bug` | Bug fix |
| `documentation` | Documentation |
| `type:perf` | Performance improvement |
| `priority:high` | High priority |
| `priority:medium` | Medium priority |
| `priority:low` | Low priority |
| `good first issue` | Good for newcomers |

### Milestones

| Milestone | Purpose |
|-----------|---------|
| `0.x.0` | Features for next minor release |
| `0.x.1` | Urgent hotfix (created as needed) |
| `Backlog` | Low priority / timing undecided |

### Creating Issues

```bash
# From CLI
gh issue create --title "Title" --body "Description" --label "enhancement,priority:medium" --milestone "0.6.0"

# Or use GitHub Web UI
```

### Linking PRs and Issues

Include `Fixes #123` in PR description to auto-close the issue on merge.

### Working on Issues

When starting work on an issue:

1. **Assign yourself** to the issue
2. **Create a feature branch**: `feature/issue-{number}-short-description`
3. **Open a Draft PR early** (optional but recommended for visibility)
4. **Comment on the issue** if it will take multiple days

This keeps parallel development coordination simple without extra tooling.