@m2015agg/git-skill 0.2.0 → 0.2.1
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.
- package/README.md +39 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,38 @@
|
|
|
1
1
|
# @m2015agg/git-skill
|
|
2
2
|
|
|
3
|
-
Git history intelligence for LLMs
|
|
3
|
+
**Git history intelligence for LLMs.** Gives AI agents institutional memory over a codebase's evolution, decisions, and health trends.
|
|
4
|
+
|
|
5
|
+
## Why This Exists
|
|
6
|
+
|
|
7
|
+
AI coding agents start every session blind. They don't know that `chat.py` has been edited 209 times and is the most volatile file in your project. They don't know you reverted that RAG optimization last week because it broke prod. They don't know the codebase just went through a major refactor and things are stabilizing.
|
|
8
|
+
|
|
9
|
+
**git-skill fixes this.** It indexes your entire git history into a local SQLite cache, computes analytics (churn hotspots, coupling, decision points, quality metrics), and writes a health summary directly into Claude Code's memory system — so every new session starts with full awareness.
|
|
10
|
+
|
|
11
|
+
### What It Solves
|
|
12
|
+
|
|
13
|
+
- **"We tried that already"** — Enrichment data tracks what was tried, reverted, and why. Agents stop re-suggesting failed approaches.
|
|
14
|
+
- **"Why does this keep breaking?"** — Churn hotspots and fix-on-fix metrics surface files that are thrashing. Agents flag risk before touching them.
|
|
15
|
+
- **"Who knows this code?"** — Author expertise mapping shows who has the most context on any file or directory.
|
|
16
|
+
- **"What happened while I was gone?"** — Decision points, trends, and release notes give a complete picture of codebase evolution.
|
|
17
|
+
- **"The agent has no memory"** — The `context-update` command writes codebase health directly into Claude's memory system. Every session starts informed.
|
|
18
|
+
|
|
19
|
+
### How It Fits Together
|
|
20
|
+
|
|
21
|
+
```
|
|
22
|
+
git history ──→ SQLite cache ──→ Analytics ──→ Claude Memory
|
|
23
|
+
(commits, (indexed, (hotspots, (auto-loaded
|
|
24
|
+
diffs, searchable) trends, every session)
|
|
25
|
+
branches) decisions)
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
Three layers of intelligence, each useful independently:
|
|
29
|
+
1. **Raw data** — every commit, file change, branch, and tag indexed and searchable
|
|
30
|
+
2. **Derived analytics** — churn hotspots, file coupling, decision points, author expertise, quality metrics
|
|
31
|
+
3. **LLM enrichments** — AI-analyzed intent, reasoning, and impact per commit (optional)
|
|
32
|
+
|
|
33
|
+
The `context-update` command bridges git-skill to Claude's memory system, writing a concise health summary that `findRelevantMemories` loads at session start.
|
|
34
|
+
|
|
35
|
+
---
|
|
4
36
|
|
|
5
37
|
## Install
|
|
6
38
|
|
|
@@ -182,6 +214,12 @@ Claude can read the config, run the commands, and interpret the results. When in
|
|
|
182
214
|
- [`@m2015agg/context7-skill`](https://github.com/m2015agg/context7-skill) — Library docs cache
|
|
183
215
|
- `@m2015agg/git-skill` — Git history intelligence
|
|
184
216
|
|
|
217
|
+
## Detailed Documentation
|
|
218
|
+
|
|
219
|
+
- [Design Spec](docs/specs/2026-03-31-git-skill-design.md) — Full architecture, schema, algorithms, and test strategy
|
|
220
|
+
- [GeorgeWorks: Memory Integration](docs/specs/context-injection.md) — How context-update writes to Claude's memory system, internal architecture of `findRelevantMemories`, consolidation phases, and thresholds
|
|
221
|
+
- [Opus Verification Layer](docs/specs/opus-verification-layer.md) — Concept for pre-commit AI verification that catches reverted re-introductions and thrashing patterns
|
|
222
|
+
|
|
185
223
|
## License
|
|
186
224
|
|
|
187
225
|
MIT
|