You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor: rename bolokonon to vibed-coding in configs and docs
Update release-please config files and documentation references to reflect the project name change from 'bolokonon' to 'vibed-coding'. This includes configuration values, file paths, and database schema references.
- A commit-insights layer that computes a simple persona + timing + category stats from commit messages only: [computeAnalysisInsights](file:///Users/devakone/Projects/bolokonon/packages/core/src/index.ts#L1005-L1244)
26
-
- A v2 “axes → persona → cards” layer that computes 6 axes and then maps to personas: [computeVibeFromCommits](file:///Users/devakone/Projects/bolokonon/packages/core/src/vibe.ts#L1358-L1493) and [detectVibePersona](file:///Users/devakone/Projects/bolokonon/packages/core/src/vibe.ts#L812-L967)
25
+
- A commit-insights layer that computes a simple persona + timing + category stats from commit messages only: [computeAnalysisInsights](file:///Users/devakone/Projects/vibed-codingn/packages/core/src/index.ts#L1005-L1244)
26
+
- A v2 “axes → persona → cards” layer that computes 6 axes and then maps to personas: [computeVibeFromCommits](file:///Users/devakone/Projects/vibed-codingn/packages/core/src/vibe.ts#L1358-L1493) and [detectVibePersona](file:///Users/devakone/Projects/vibed-codingn/packages/core/src/vibe.ts#L812-L967)
27
27
28
28
### What “agentic” detection exists right now
29
29
30
30
**1) Bot/automation filtering**
31
31
- We filter likely bot commits by email substrings (e.g., dependabot, renovate, github-actions) and subject patterns.
32
32
- This cleans up human behavioral signals but can hide “agent commits” if they come from bot-like emails.
- We collect “agent evidence” by matching a keyword regex against the commit subject.
38
38
- Persona “Multi-Agent Orchestrator” in the insights layer is currently driven by “chunkiness” + file-change breadth + this keyword evidence.
39
39
40
-
Implementation: [computeAnalysisInsights](file:///Users/devakone/Projects/bolokonon/packages/core/src/index.ts#L1026-L1199) and [detectPersona](file:///Users/devakone/Projects/bolokonon/packages/core/src/index.ts#L296-L430)
40
+
Implementation: [computeAnalysisInsights](file:///Users/devakone/Projects/vibed-codingn/packages/core/src/index.ts#L1026-L1199) and [detectPersona](file:///Users/devakone/Projects/vibed-codingn/packages/core/src/index.ts#L296-L430)
41
41
42
42
**3) Broad-change proxies**
43
43
- Vibe v2 uses “automation heaviness” and “surface area per change” (via file paths / episodes) as indirect proxies.
@@ -134,7 +134,7 @@ Multi-agent orchestration often shows up as:
134
134
- consistent PR templates/checklists
135
135
- high squash-merge rate (agentic PR hygiene)
136
136
137
-
We have a clear target schema in [vibe-metrics-v2.md](file:///Users/devakone/Projects/bolokonon/docs/architecture/vibe-metrics-v2.md#L173-L265), but it’s not currently populated.
137
+
We have a clear target schema in [vibe-metrics-v2.md](file:///Users/devakone/Projects/vibed-codingn/docs/architecture/vibe-metrics-v2.md#L173-L265), but it’s not currently populated.
138
138
139
139
### B) Branch topology / parallelism (medium signal)
140
140
@@ -152,7 +152,7 @@ Mapping commits to PRs enables:
152
152
- “how many commits are squash merges”
153
153
- “how chunkiness differs inside PRs vs direct-to-main”
0 commit comments