whogitit 1.0.0

Track AI-generated code at line-level granularity
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
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145

# status

Check pending AI attribution changes before committing.

## Synopsis

```bash
whogitit status
```

## Description

The `status` command shows the current state of the pending buffer, which accumulates AI attribution data during your Claude Code session. This helps you understand what will be attached to your next commit.

## Examples

### With Pending Changes

```bash
whogitit status
```

Output:

```text
Pending AI attribution:
  Session: 7f3a-4b2c-9d1e-8a7b
  Files: 3
  Edits: 7
  Lines: 145
  Age: 2 hours ago

Run 'git commit' to finalize attribution.
```

### No Pending Changes

```bash
whogitit status
```

Output:

```text
No pending AI attribution.
```

### Stale Pending Buffer

If the pending buffer is older than the configured threshold
(`analysis.max_pending_age_hours`, default 24), a warning is displayed:

```text
Pending AI attribution:
  Session: 7f3a-4b2c-9d1e-8a7b
  Files: 3
  Edits: 7
  Lines: 145
  Age: 2 days ago

⚠️  Warning: This pending buffer is stale (> 24 hours old).
   Run 'whogitit clear' if these changes are no longer relevant.
```

## Output Details

| Field | Description |
|-------|-------------|
| Session | The AI session ID |
| Files | Number of files with captured changes |
| Edits | Total number of edit operations captured |
| Lines | Approximate lines affected |
| Age | How long since the first capture |

## Use Cases

### Pre-Commit Check

Before committing, verify what attribution data will be attached:

```bash
whogitit status
git status
git commit -m "Add new feature"
```

### Debugging Hook Issues

If attribution isn't being captured, check if any data is pending:

```bash
# Make an edit with Claude Code
# Then check status
whogitit status

# If empty, hooks may not be configured correctly
```

### Clearing Stale Data

If you've been working but don't want to commit the AI attribution:

```bash
whogitit status
# Shows stale pending data

whogitit clear
# Clears the pending buffer

whogitit status
# No pending AI attribution.
```

## Related Commands

### clear

Discard pending changes without committing:

```bash
whogitit clear
```

This removes the `.whogitit-pending.json` file, discarding all captured attribution data for the current session.

### init

If `status` shows issues, reinitialize:

```bash
whogitit init
```

This reinstalls hooks and reconfigures git.

## Notes

- The pending buffer is stored in `.whogitit-pending.json` in your repository root
- This file is typically in `.gitignore` and should not be committed
- The pending buffer is automatically cleared after a successful commit

## See Also

- [Quick Start](../../getting-started/quick-start.md) - Basic workflow
- [Hook System](../../reference/hooks.md) - How capture works