@boshu2/vibe-check 2.2.0 → 2.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/CHANGELOG.md +1 -1
- package/README.md +46 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
package/README.md
CHANGED
|
@@ -73,12 +73,38 @@ npx @boshu2/vibe-check dashboard
|
|
|
73
73
|
|
|
74
74
|
## What It Measures
|
|
75
75
|
|
|
76
|
+
### Core Metrics
|
|
77
|
+
|
|
76
78
|
| Metric | Question | Target |
|
|
77
79
|
|--------|----------|--------|
|
|
78
80
|
| **Trust Pass Rate** | Does the code stick? | >95% |
|
|
79
81
|
| **Rework Ratio** | Building or debugging? | <30% |
|
|
80
82
|
| **Debug Spirals** | Are you stuck? | 0 active |
|
|
81
83
|
|
|
84
|
+
### Enhanced Metrics (v2.2.0)
|
|
85
|
+
|
|
86
|
+
Three deeper metrics for understanding development habits:
|
|
87
|
+
|
|
88
|
+
| Metric | Question | Target |
|
|
89
|
+
|--------|----------|--------|
|
|
90
|
+
| **Tracer Bullet Ratio** | Are you validating assumptions? | >20% |
|
|
91
|
+
| **Investigation Time** | How much hidden debugging? | 0 min |
|
|
92
|
+
| **Domain Cohesion** | Are changes focused? | >80% |
|
|
93
|
+
|
|
94
|
+
**Tracer Bullets** — Use `tracer:` or `tb:` prefix for validation commits:
|
|
95
|
+
|
|
96
|
+
```
|
|
97
|
+
tracer(auth): validate OAuth token refresh
|
|
98
|
+
tb(api): test streaming endpoint response
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
- Tracers **before features** = proactive validation ✅
|
|
102
|
+
- Tracers **before fixes** = reactive debugging ❌ (too late!)
|
|
103
|
+
|
|
104
|
+
**Investigation Gaps** — Detects hidden debugging time (15-120 min gaps followed by fix commits).
|
|
105
|
+
|
|
106
|
+
**Domain Cohesion** — Measures how scattered changes are. Single-domain commits indicate clean vertical slices.
|
|
107
|
+
|
|
82
108
|
---
|
|
83
109
|
|
|
84
110
|
## The 12 Failure Patterns
|
|
@@ -190,12 +216,31 @@ vibe-check insights # Your spiral patterns
|
|
|
190
216
|
### Code Quality
|
|
191
217
|
|
|
192
218
|
```bash
|
|
193
|
-
vibe-check audit # Scan for monoliths, test gaps, TODOs
|
|
219
|
+
vibe-check audit # Scan for monoliths, test gaps, TODOs, eldritch horrors
|
|
194
220
|
vibe-check modularity # Pattern-aware modularity analysis
|
|
195
221
|
vibe-check modularity --verbose # Detailed breakdown with metrics
|
|
196
222
|
vibe-check modularity -f json # JSON output for CI integration
|
|
197
223
|
```
|
|
198
224
|
|
|
225
|
+
#### Audit Command (v2.2.0)
|
|
226
|
+
|
|
227
|
+
The `audit` command now includes **Eldritch Horror Detection**—identifying oversized functions that are symptomatic of AI-generated code gone wrong:
|
|
228
|
+
|
|
229
|
+
```
|
|
230
|
+
👹 Eldritch Horrors (oversized functions):
|
|
231
|
+
src/services/auth.ts:45
|
|
232
|
+
handleAuthentication: 523 lines (CRITICAL)
|
|
233
|
+
src/api/routes.ts:120
|
|
234
|
+
processRequest: 287 lines (warning)
|
|
235
|
+
```
|
|
236
|
+
|
|
237
|
+
| Severity | Threshold | What It Means |
|
|
238
|
+
|----------|-----------|---------------|
|
|
239
|
+
| Warning | >200 lines | Hard to understand |
|
|
240
|
+
| Critical | >500 lines | Impossible to maintain |
|
|
241
|
+
|
|
242
|
+
Supports: TypeScript, JavaScript, Python, Go
|
|
243
|
+
|
|
199
244
|
### Tools
|
|
200
245
|
|
|
201
246
|
```bash
|